Update teams-developer-portal.md

Added new content

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/build-and-test/teams-developer-portal.md
92
13
link
:white_check_mark:

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

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

File
Status
Preview URL
Details

msteams-platform/concepts/build-and-test/teams-developer-portal.md
:white_check_mark:Succeeded
View

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/build-and-test/teams-developer-portal.md
92
13
link
:white_check_mark:

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/build-and-test/teams-developer-portal.md
93
15
link
:white_check_mark:

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

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

File
Status
Preview URL
Details

msteams-platform/concepts/build-and-test/teams-developer-portal.md
:white_check_mark:Succeeded
View

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/build-and-test/teams-developer-portal.md
93
15
link
:white_check_mark:

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

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

File
Status
Preview URL
Details

msteams-platform/concepts/build-and-test/teams-developer-portal.md
:white_check_mark:Succeeded
View

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/build-and-test/teams-developer-portal.md
93
15
link
:white_check_mark:

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

Docs Build status updates of commit 27ea480:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/concepts/build-and-test/teams-developer-portal.md
:warning:Warning
View
Details

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

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

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

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

msteams-platform/assets/images/tdp/tdp_publish-app.png
:white_check_mark:Succeeded
View

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

msteams-platform/concepts/build-and-test/teams-developer-portal.md

Line 230, Column 5: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 230, Column 5: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/' will be broken in isolated environments. Replace with a relative link.

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/build-and-test/teams-developer-portal.md
93
15
link
:white_check_mark:

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

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

File
Status
Preview URL
Details

msteams-platform/concepts/build-and-test/teams-developer-portal.md
:bulb:Suggestion
View
Details

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

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

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

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

msteams-platform/assets/images/tdp/tdp_publish-app.png
:white_check_mark:Succeeded
View

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

msteams-platform/concepts/build-and-test/teams-developer-portal.md

Line 222, Column 5: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/microsoftteams/platform/' will be broken in isolated environments. Replace with a relative link.

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/build-and-test/teams-developer-portal.md
93
15
link
:white_check_mark:

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

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

File
Status
Preview URL
Details

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

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

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

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

msteams-platform/assets/images/tdp/tdp_publish-app.png
:white_check_mark:Succeeded
View

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

msteams-platform/concepts/build-and-test/teams-developer-portal.md
:white_check_mark:Succeeded
View

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/build-and-test/teams-developer-portal.md
93
15
link
:white_check_mark:

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

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

File
Status
Preview URL
Details

msteams-platform/concepts/build-and-test/teams-developer-portal.md
:warning:Warning
View
Details

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

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

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

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

msteams-platform/assets/images/tdp/tdp_publish-app.png
:white_check_mark:Succeeded
View

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

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

msteams-platform/concepts/build-and-test/teams-developer-portal.md

Line 169, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'Publish app' is duplicated. Within an article, alt text must be unique.
Line 211, Column 5: [Warning: duplicate-alt-text - See documentation] Alt text 'Publish app' is duplicated. Within an article, alt text must be unique.

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/build-and-test/teams-developer-portal.md
93
15
link
:white_check_mark:

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/build-and-test/teams-developer-portal.md
93
15
link
:white_check_mark:

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

Docs Build status updates of commit 509e72e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

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

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

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

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

msteams-platform/assets/images/tdp/tdp_publish-app.png
:white_check_mark:Succeeded
View

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

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

msteams-platform/concepts/build-and-test/teams-developer-portal.md
:white_check_mark:Succeeded
View

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/build-and-test/teams-developer-portal.md
93
15
link
:white_check_mark:

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

Docs Build status updates of commit 343ff34:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

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

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

msteams-platform/assets/images/tdp/tdp_configure_1.PNG
:white_check_mark:Succeeded
View

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

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

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

msteams-platform/assets/images/tdp/tdp_publish-app.png
:white_check_mark:Succeeded
View

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

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

msteams-platform/concepts/build-and-test/teams-developer-portal.md
:white_check_mark:Succeeded
View

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/build-and-test/teams-developer-portal.md
93
15
link
:white_check_mark:

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

Docs Build status updates of commit 43664ed:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

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

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

msteams-platform/assets/images/tdp/tdp_configure_1.PNG
:white_check_mark:Succeeded
View

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

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

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

msteams-platform/assets/images/tdp/tdp_publish-app.png
:white_check_mark:Succeeded
View

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

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

msteams-platform/concepts/build-and-test/teams-developer-portal.md
:white_check_mark:Succeeded
View

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/build-and-test/teams-developer-portal.md
92
17
link
:white_check_mark:

msteams-platform/kss-tracking.yml
87
30
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 002d5bf:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

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

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

msteams-platform/assets/images/tdp/tdp_configure_1.PNG
:white_check_mark:Succeeded
View

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

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

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

msteams-platform/assets/images/tdp/tdp_publish-app.png
:white_check_mark:Succeeded
View

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

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

msteams-platform/concepts/build-and-test/teams-developer-portal.md
:white_check_mark:Succeeded
View

msteams-platform/kss-tracking.yml
: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 c4bcddf:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

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

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

msteams-platform/assets/images/tdp/tdp_configure_1.PNG
:white_check_mark:Succeeded
View

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

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

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

msteams-platform/assets/images/tdp/tdp_publish-app.png
:white_check_mark:Succeeded
View

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

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

msteams-platform/concepts/build-and-test/teams-developer-portal.md
:white_check_mark:Succeeded
View

msteams-platform/kss-tracking.yml
:white_check_mark:Succeeded
View

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/build-and-test/teams-developer-portal.md
92
17
link
:white_check_mark:

msteams-platform/kss-tracking.yml
87
30
link
:white_check_mark:

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/build-and-test/teams-developer-portal.md
92
17
link
:white_check_mark:

msteams-platform/kss-tracking.yml
87
30
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 ede8734:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

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

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

msteams-platform/assets/images/tdp/tdp_configure_1.PNG
:white_check_mark:Succeeded
View

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

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

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

msteams-platform/assets/images/tdp/tdp_publish-app.png
:white_check_mark:Succeeded
View

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

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

msteams-platform/concepts/build-and-test/teams-developer-portal.md
:white_check_mark:Succeeded
View

msteams-platform/kss-tracking.yml
:white_check_mark:Succeeded
View

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/build-and-test/teams-developer-portal.md
92
17
link
:white_check_mark:

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

Docs Build status updates of commit 3765f20:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

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

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

msteams-platform/assets/images/tdp/tdp_configure_1.PNG
:white_check_mark:Succeeded
View

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

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

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

msteams-platform/assets/images/tdp/tdp_publish-app.png
:white_check_mark:Succeeded
View

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

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

msteams-platform/concepts/build-and-test/teams-developer-portal.md
:white_check_mark:Succeeded
View

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/build-and-test/teams-developer-portal.md
92
17
link
:white_check_mark:

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

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

File
Status
Preview URL
Details

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

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

msteams-platform/assets/images/tdp/tdp_configure_1.PNG
:white_check_mark:Succeeded
View

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

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

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

msteams-platform/assets/images/tdp/tdp_publish-app.png
:white_check_mark:Succeeded
View

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

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

msteams-platform/concepts/build-and-test/teams-developer-portal.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 939c645:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

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

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

msteams-platform/assets/images/tdp/tdp_configure_1.PNG
:white_check_mark:Succeeded
View

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

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

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

msteams-platform/assets/images/tdp/tdp_publish-app.png
:white_check_mark:Succeeded
View

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

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

msteams-platform/concepts/build-and-test/teams-developer-portal.md
:white_check_mark:Succeeded
View

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/build-and-test/teams-developer-portal.md
92
17
link
:white_check_mark:

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

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

File
Status
Preview URL
Details

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

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

msteams-platform/assets/images/tdp/tdp_configure_1.PNG
:white_check_mark:Succeeded
View

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

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

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

msteams-platform/assets/images/tdp/tdp_publish-app.png
:white_check_mark:Succeeded
View

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

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

msteams-platform/concepts/build-and-test/teams-developer-portal.md
:white_check_mark:Succeeded
View

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/build-and-test/teams-developer-portal.md
92
17
link
:white_check_mark:

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

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

File
Status
Preview URL
Details

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

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

msteams-platform/assets/images/tdp/tdp_configure_1.PNG
:white_check_mark:Succeeded
View

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

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

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

msteams-platform/assets/images/tdp/tdp_publish-app.png
:white_check_mark:Succeeded
View

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

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

msteams-platform/concepts/build-and-test/teams-developer-portal.md
:white_check_mark:Succeeded
View

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/build-and-test/teams-developer-portal.md
92
17
link
:white_check_mark:

msteams-platform/messaging-extensions/how-to/search-commands/define-search-command.md
89
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 b09c13d:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

msteams-platform/messaging-extensions/how-to/search-commands/define-search-command.md
:x:Error

Details

msteams-platform/messaging-extensions/how-to/search-commands/define-search-command.md

Line 20, Column 1: [Error: invalid-zone] Invalid pivot "<node-js>". Pivot must be a comma-delimited list of pivot names. Pivot names must be lower-case and contain only letters, numbers or dashes.
Line 26, Column 1: [Error: invalid-zone] Invalid pivot "<asp-net-core>". Pivot must be a comma-delimited list of pivot names. Pivot names must be lower-case and contain only letters, numbers or dashes.
Line 28, Column 1: [Error: include-not-found] Invalid include link: '~/includes/feedback.md'.
Line 20, Column 18: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'node-js' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 26, Column 18: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'asp-net-core' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/build-and-test/teams-developer-portal.md
92
17
link
:white_check_mark:

msteams-platform/messaging-extensions/how-to/search-commands/define-search-command.md
89
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 40a97c1:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

msteams-platform/messaging-extensions/how-to/search-commands/define-search-command.md
:x:Error

Details

msteams-platform/messaging-extensions/how-to/search-commands/define-search-command.md

Line 20, Column 1: [Error: invalid-zone] Invalid attribute "pivot". Values must be enclosed in double quotes.
Line 26, Column 1: [Error: invalid-zone] Invalid attribute "pivot". Values must be enclosed in double quotes.

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/build-and-test/teams-developer-portal.md
92
17
link
:white_check_mark:

msteams-platform/messaging-extensions/how-to/search-commands/define-search-command.md
89
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 12a6c1c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

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

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

msteams-platform/assets/images/tdp/tdp_configure_1.PNG
:white_check_mark:Succeeded
View

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

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

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

msteams-platform/assets/images/tdp/tdp_publish-app.png
:white_check_mark:Succeeded
View

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

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

msteams-platform/concepts/build-and-test/teams-developer-portal.md
:white_check_mark:Succeeded
View

msteams-platform/messaging-extensions/how-to/search-commands/define-search-command.md
:white_check_mark:Succeeded
View

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/build-and-test/teams-developer-portal.md
92
17
link
:white_check_mark:

msteams-platform/messaging-extensions/how-to/search-commands/define-search-command.md
89
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 1ab1fcb:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

msteams-platform/messaging-extensions/how-to/search-commands/define-search-command.md
:x:Error

Details

msteams-platform/messaging-extensions/how-to/search-commands/define-search-command.md

Line 21, Column 1: [Error: include-not-found] Invalid include link: 'includes/how-to/search-commands/respond-to-search.md'.
Line 25, Column 1: [Error: include-not-found] Invalid include link: 'includes/how-to/search-commands/respond-to-search.md'.

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/build-and-test/teams-developer-portal.md
92
17
link
:white_check_mark:

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

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

File
Status
Preview URL
Details

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

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

msteams-platform/assets/images/tdp/tdp_configure_1.PNG
:white_check_mark:Succeeded
View

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

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

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

msteams-platform/assets/images/tdp/tdp_publish-app.png
:white_check_mark:Succeeded
View

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

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

msteams-platform/concepts/build-and-test/teams-developer-portal.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

Closing this PR as the content is moved to this PR as per the request:
https://github.com/MicrosoftDocs/msteams-docs/pull/5466/


Add support PHP 8.1 to github actions.

Q
A

Is bugfix?
❌

New feature?
✔

Breaks BC?
❌

closed in favor https://github.com/yiisoft/yii2-symfonymailer/pull/66


[ZEPPELIN-5321] Missing links of some interpreters in index page and link menu

What is this PR for?
Fix missing interpreter links in document page
What type of PR is it?
[Documentation]
What is the Jira issue?

https://issues.apache.org/jira/browse/ZEPPELIN-5321

How should this be tested?

Check updated document locally

Questions:

Does the licenses files need update? No
Is there breaking changes for older versions? No
Does this needs documentation? No

Thanks @cuspymd for the contribution, LGTM


can not get git status result when using "Repository api in vscode.git"

VS Code Version:  ^1.74.0
OS Version:

Steps to Reproduce:
As i write an extension in which i want to get the git status of current workspace.  I notice that i could get the "vscode.git" extension from  "extensions.getExtension('vscode.git')".  Then i try to get its repository and call its method status(), however this method only return a void, so how could i  get the similar result of in my code  as that by "git status" in shell.
i write it as below:
const gitExtension = extensions.getExtension<GitExtension>('vscode.git');
if (!gitExtension?.isActive) {
	await gitExtension?.activate();
}
let gitApi = gitExtension?.exports.getAPI(1);
let [git] = gitApi.repositories;
let result = await git.status();   //here could only return void

so how could i get the "git status" result any way ?
Regards

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.88.1. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

i run "restart to update" from vscode menu, and  update the version to v1.88.0 automatically, which show date of "2024-04-03". I think this is the latest version available online. And i try it again, the  status() still return back an undefined.

When you call repository.status() then the vscode.git extension will execute git status will parse the output and it will update the model for the repository. After calling status() you can access the model using repository.state.
https://github.com/microsoft/vscode/blob/31fba19dcf3432e074d6f843cbb3f569248d29cf/extensions/git/src/api/api1.ts#L33-L34

i get the content at repository.state as Iszomoru commented.  It works for me, : )  thank you very much for the quick and helpful reply.

I want to get the list of files in staging .how can I get that

@seema-s7, use the indexChanges property:
https://github.com/microsoft/vscode/blob/09e9d305a2d50bdbd4d2561d3902b0d842ac22a6/extensions/git/src/api/api1.ts#L45-L46


simulation of paraboloid mirror

It comes some confusions when I go through my simulation of paraboloid mirror. I will list them below.

The mirror
I want the mirror could collimate the divergent beam in horizontal orientation, so I set  the O.E. orientation angle of the mirror to 90 degrees.
When I changed the angular divergence X(+ & -) of the source into a considerable value (e.g. 1 rad), the imaging results showed two light spots.
I wonder whether two symmetrical mirrors have actually been set in the paraboloid module?
The orientation of center light
An obvious question showed up If my presume above were true: I set up the incident angle, the source plane distance and the paraboloid parameter so that I can define the point “A” at which the center light acts with the parabolic collection mirror. Then I set up the dimensions of the mirror(X,Y half widths), so that I have construct the shape of one pair of dual parabolic mirrors. After I finish these steps, the another one pair of the dual parabolic mirrors would be created by symmetry through the axis of the parabola.
Here comes the question: If I choose a gaussian source, the center light of the source is the ray that initiated from the center of gaussian spot to the point “A” which firstly defines the parabolic mirror that I construct, In the design of a spectrometer. It is hoped that the center light coincides with the parabolic mirrors symmetrical axis, the situation above makes the gaussian source plot somewhat asymmetric for parabolic symmetry axis.
What could I attempt to make the center light coincide with the parabolic symmetry axis?

The movement of the source
To be honest, I am so confused about those items in source movement. It seems that I could construct a polar coordinate system which the origin is at point “A”, then I could freely change the position of the source in the space. What confuse me is the item below.
What would happen if I change those offsets in O.E. and SOURCE reference frames. after I have set up the angle of incidence, distance from O.E. and Z-rotation, i.e. whether there is a priority between the change of incident arm and angle with the change of the reference frame?

In my spectrometer layout design, I hope to make all the symmetry axes of meridional-oriental O.E. (e.g. focus mirror, grating) are coincident with the symmetry axis of the dual parabolic mirrors and the center light when the source is stable. However in the reference frame logic of SHADOW, when the source movement is taken into consideration, the layout seems to be so strange. In other words, I do not want my layout to be influenced by the movement of source. What parameter should I set extra to achieve my goal?

Thank you so much!
parabolic collimate mirror.zip

1- I wonder whether two symmetrical mirrors have actually been set in the paraboloid module?
Actually yes. Shadow calculates the intercept with the infinite surface. Then, from the two posible solutions of the conic equation, it takes the closer one.

2 > Here comes the question: If I choose a gaussian source, the center light of the source is the ray that initiated from the center of gaussian spot to the point “A” which firstly defines the parabolic mirror that I construct, In the design of a spectrometer. It is hoped that the center light coincides with the parabolic mirrors symmetrical axis, the situation above makes the gaussian source plot somewhat asymmetric for parabolic symmetry axis.
What could I attempt to make the center light coincide with the parabolic symmetry axis?
This is difficult. I have no answer.
I tried the parabola with the beam in normal incidence (0 degrees with the normal) and placing the source at the parabola focus. You get something collimated, but the footprint on the mirror is not good (shadow takes the closer solution and we want the farther one).
3 - The application of the movements has a sequential order (I do not remember, I should look to the code). I suggest not to move source and OE at the same time.
Note that the source and OE movements are set to see the beam displacement therefore the origins (optical axis) still corresponds to the non-deviated beam.
What I suggest is to simulate only one reflection (not the two reflections at the same time) and rotate the element (and translate it) to see the effect of misalignment.
Sorry for not being more helpful!


[GITHUB-4] Fix removal of the anonymous user

@lobsterdore can you take a quick look pls

@wojtek-oledzki Hello stranger :)
When are you seeing this issue? I haven't encountered a situation where I need become: yes on the anon user removal.

@lobsterdore try on a system where you don't have root.
TASK [sansible.mysql : Remove anonymous user] **********************************
fatal: [***]: FAILED! => {"changed": false, "failed": true, "msg": "unable to connect to database, check login_user and login_password are correct or /home/ubuntu/.my.cnf has the credentials. Exception message: (1698, \"Access denied for user 'root'@'localhost'\")"}

this is the first pass on plain Xenial server. The become: yes is not proper solution anyway - it only works if the mysql.root_login is set to root

@lobsterdore let me have a quick check - I will ensure the "root" user + passwd first and then remove the anonymous user...

@lobsterdore works, take a look again.

LGTM 👍
Closes #4


Error when using self hosted GitLab with subpath + GitLab filler processor

I'm experiencing an issue because our self hosted gitlab instance runs under a subpath.
e.g. git.company.com/gitlab
When trying to access git.company.com/gitlab/genc/infrastructure/docker the GitLab Filler Processor tries to call
git.company.com/projects/gitlab/genc/infrastructure/docker instead of git.company.com/gitlab/projects/genc/infrastructure/docker
-->
http://localhost:8080/api/gitlab/rest/git.company.com/projects/gitlab%2Fgenc%2Finfrastructure%2Fdocker
Maybe related to: https://github.com/immobiliare/backstage-plugin-gitlab/issues/236
Everything else works fine, just the gitlab filler processor does not.

Can you post your Backstage gitlab configurations?

integrations:
  gitlab:
    - host: git.company.com
      apiBaseUrl: https://git.company.com/gitlab/api/v4
      baseUrl: https://git.company.com/gitlab
      token: ${GITLAB_TOKEN}

proxy:
  '/gitlabci':
    target: 'https://git.company.com/gitlab/api/v4'
    allowedMethods: ['GET', 'POST']
    headers:
      PRIVATE-TOKEN: '${GITLAB_TOKEN}'

gitlab: #for gitlab plugin: https://github.com/immobiliare/backstage-plugin-gitlab
  defaultCodeOwnersPath: .gitlab/CODEOWNERS

can you post the request error ?

The request is a simple get http://localhost:8080/api/gitlab/rest/git.company.com/projects/gitlab%2Fgenc%2Finfrastructure%2Fdocker that results in a 404 not found

I mean the request done by the server. Because the client's request is correct, it should be formed this way.

[1] 2023-11-23T14:34:57.936Z backstage info ::1 - - [23/Nov/2023:14:34:57 +0000] "GET /api/gitlab/rest/git.company.com/projects/gitlab%2Fgenc%2Finfrastructure%2Fdocker?? HTTP/1.1" 404 35 "http://localhost:3000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36 Edg/<IP_ADDRESS>" type=incomingRequest
[1] 2023-11-23T14:34:57.940Z gitlab debug [HPM] Rewriting path from "/api/gitlab/rest/git.company.com/projects/gitlab%2Fgenc%2Finfrastructure%2Fdocker??" to "/gitlab/api/v4/projects/gitlab%2Fgenc%2Finfrastructure%2Fdocker??" type=plugin

[1] 2023-11-23T14:34:58.036Z backstage info ::1 - - [23/Nov/2023:14:34:58 +0000] "GET /api/gitlab/rest/git.company.com/projects/gitlab%2Fgenc%2Finfrastructure%2Fdocker?? HTTP/1.1" 404 35 "http://localhost:3000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36 Edg/<IP_ADDRESS>" type=incomingRequest
[1] 2023-11-23T14:34:58.038Z gitlab debug [HPM] Rewriting path from "/api/gitlab/rest/git.company.com/projects/gitlab%2Fgenc%2Finfrastructure%2Fdocker??" to "/gitlab/api/v4/projects/gitlab%2Fgenc%2Finfrastructure%2Fdocker??" type=plugin
[1] 2023-11-23T14:34:58.139Z backstage info ::1 - - [23/Nov/2023:14:34:58 +0000] "GET /api/gitlab/rest/git.company.com/projects/gitlab%2Fgenc%2Finfrastructure%2Fdocker?? HTTP/1.1" 404 35 "http://localhost:3000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36 Edg/<IP_ADDRESS>" type=incomingRequest

The 404 error occurs because the project is prefixed with the subpath from our gitlab instance /gitlab
Rewriting path from "/api/gitlab/rest/git.company.com/projects/gitlab%2Fgenc%2Finfrastructure%2Fdocker??" to "/gitlab/api/v4/projects/gitlab%2Fgenc%2Finfrastructure%2Fdocker??"
The right path should be /api/gitlab/rest/git.company.com/projects/genc%2Finfrastructure%2Fdocker??

I think the problem is related to the gitlab configuration only using the host config value instead of the baseUrl specified here

mm strange, can you post the annonations?

This error only occurs, when we don't set any annotation.
When setting gitlab.com/project-slug: genc/applications/genc/infrastructure/docker everthing works as expected

If you go to backstage entity without setting the annotation you click on three dots in the top right corner you click inspect entity, and you can see the annotations assigned by the processor. Can you post the value?

gitlab.com/instance
    git.company.com/gitlab
gitlab.com/project-slug
    gitlab/genc/applications/playground/dfl-showcase-test

Ok, the project slug is wrong. I created a PR to fix it.

Amazing, thanks for your quick help!

I created a new prerelease. Can you test it? Let me know if it works now!

That fixed it! Thank you again :)

Ok thank you, I release the new version.


Missing imports in regressions

Description

Following #5426 some regressions were breaking because of missing timedelta imports
Related Issue

N/A; Just noticed the issue and saw where it came from. Quick fix 👍🏽
Motivation and Context

Requires Documentation Change

How Has This Been Tested?

Regressions are all passing again.
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] Refactor (non-breaking change which improves implementation)
[ ] Performance (non-breaking change which improves performance. Please add associated performance test and results)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Non-functional change (xml comments/documentation/etc)

Checklist:

[x] My code follows the code style of this project.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.
[x] My branch follows the naming convention bug-<issue#>-<description> or feature-<issue#>-<description>

Included in https://github.com/QuantConnect/Lean/pull/5425/commits/140da1bf880f339449f1f94e431d36d5d2355738


better type coercion : instead of cannot invoke an expression whose type lacks a call signature

TypeScript Version:  2.6.2
{
    "compilerOptions": {
        "strict": true,

Code
export interface HopeLike<T, S = void>
{
    <U>(callabale: (value: T) => U, asHoped?: (value: U) => boolean): HopeLike<U, T>;
    or<U>(callable: (parent: S, value: T) => U): this | HopeLike<U, T>;
    get(): T | void;
}

let h: HopeLike<number> = <any>void 0;
h(() => 1).or(() => '').or(p => ({})); // here is the issue, from the `.or(...`

Note that this code works well if .or call is not called twice!
A concrete usecase
const EVENT: Event<typeof source> = new Event(event, source);
const HANDLERS = hope(EVENT_EMMITTERS.get(this)!)
    (container => container.get(event)!)
// Since it is not sure this key is mapped, let's ensure, just in case.
// This' achieved by calling `.or(callback)` which will run its callback only if the `event` key is mapped
    .or(container => container.set(event, []).get(event)!)
        .get(); // were finally fetch the real result, which may be `void` as well
if (HANDLERS) for (let handler of HANDLERS)
    if (void handler.call(EVENT, EVENT, ...data) || EVENT.isPropagationStopped)
        break;

Where :

const EVENT_EMMITTERS: WeakMap<EventEmitter<any>, Map<string, EventHandlerLike<any>[]>> = new WeakMap();
The this context is instance of EventEmitter

Expected behavior:
I had expected these to be inferred after the.or second call:

parameter p as number | string
the return value to be: HopeLike<number, number> | HopeLike<U, number> | HopeLike<string, number> | HopeLike<U, string>

Actual behavior:
The error says cannot invoke an expression whose type lacks a call signature. Type '(<U>(callable: (parent: number, value: number) => U): HopeLike<number, number> | HopeLike<U, nu...'

This might be fixed by #17819; @weswigham?

Thanks @DanielRosenwasser  for your interest. As far as I can tell of your example, the union type is for signatures with same return type and but differing parameter types.
In my case, the parameter is of one type only. The return type changes depending of what happen at rutime: the callback in the .or(...) call is executed only if the computed value from previous HopeLike<T, S>(...) call were not satisfied (according to the predicate asHoped(...)).
So, no sure this might be a fix.

However, I was able to increase typing complexity, wrote a solution that worked, then striped off unnecessary code until I got a simple solution that works just as I expected (even the implementation is now tiny).
export interface HopeLike<T, S = void>
{
    <U>(map: (value: T) => U, asHoped?: (value: U) => boolean): HopeLike<U, T>;
    or(map: (parent: S) => T): HopeLike<T, S>;
    get(): T | void;
}

You may discover that the redesigned interface express something strongly different from the first version. I figured out that I wrongly implemented the solution to that my specific problem. Nonetheless, the question remains: [W]hy TypeScript cannot (yet) infer that union type of two functions to be function, thus callable ?
Therefore, I call for possible duplicates as I believe this isn't the first issue opened about...

I have reduced the problem down so it is easier to to see the issue:
type Func = (<T>() => T) | (() => void);

const callme = {} as Func;

callme(); // error

You got it clear, @sylvanaar

Duplicate of #7294


[FLINK-5640][build]configure the explicit Unit Test file suffix

There are four types of Unit Test file: *ITCase.java, *Test.java, *ITSuite.scala, *Suite.scala
File name ending with "IT.java" is integration test. File name ending with "Test.java"  is unit test.
It's clear for Surefire plugin of default-test execution to declare that "Test." is Java Unit Test.
The test file statistics:

Suite  total: 10
ITCase  total: 378
Test  total: 1008
ITSuite  total: 14

cc @rmetzger

Can you briefly explain what this fixes? Currently, it behaves exactly like you describe: The "test" phase executes the *Test.java and *Test.scala classes, and the "verify" phase executes the *ITCase.java and *ITCase.scala classes.
Also, the changes to the compiler plugin - what is the purpose and effect of setting it to "verbose"?

@StephanEwen Thank for your quickly reviewing.

<include>**/*Test.*</include>
This can clearly show what unit test's file name like, just like integration-tests does. If omitting the include, it means that all the class file except **/*ITCase.* should be unit test, not only *Test.*.

@shijinkui I think the Unite test include pattern is a good change, would merge that.
Can we exclude the changes to the compiler configuration from the initial change?

@StephanEwen have finished that.

Change looks good, thanks!
Merging this...


Kotlin enum is not working as query param [DATAJDBC-501]

umut erturk opened DATAJDBC-501 and commented
Kotlin enum as the query param is not working.
when this line runs I get an exception message:
Caused by: org.h2.jdbc.JdbcSQLDataException: Hexadecimal string with odd number of characters: "RUNNING"; SQL statement...

You can reproduce the case from given branch in the Reference URL

Reference URL: https://github.com/tirbison/spring-data-jdbc-kotlin/tree/bug/reproduce/enum-query-param

This was fixed by https://github.com/spring-projects/spring-data-relational/issues/1212


Adding throws to function signatures

Suggestion

🔍 Search Terms

throw
throws
try catch

✅ Viability Checklist

My suggestion meets these guidelines:

[x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
[x] This feature would agree with the rest of TypeScript's Design Goals.

⭐ Suggestion

I have seen that people have been asking for this for years. There are two main reasons that people want this, first to get better typing in try catch statements, and second to get the compiler to warn or error when a function that throws is called without handling the possible thrown value. As it is the goal of TypeScript to bring type safety to JavaScript, I think this would be huge in helping TypeScript developers write code that is more reliable and deterministic.
See: https://github.com/microsoft/TypeScript/issues/13219
My goal here is to propose a design that provides the desired features while being backwards compatible. In this proposal we will look at:

Adding a compiler option for strictThrows: boolean
Adding throws to function signatures.
Getters/Setters can throw, how do we handle that?
How throws is inferred.
How catch(e) is inferred in non-async functions.
Working with throws in generics and conditionals.
Updates to Promise types.
How this effects async/await.
How catch(e) is inferred in async functions

Adding a compiler option for strictThrows: boolean
With strictThrows set to false we still get the benefit of better typing in try catch statements, however the compiler does not warn/error when functions that throw are called and not handled. There are a few other nuances that will be addressed in later sections.
Adding throws to function signatures.
The thrown type is declared following the return signature separated by throws. If there is no throws <type> in the signature it is equivalent to throws never which means that the function does not throw -- this is important for generics which we will discuss later. In intellisense we can omit the throws clause if the thrown type is never, however in this proposal I am going to include them for clarity.
function test(): string {...}

type test = typeof test;
//   ^? () => string throws never

function testThrows(): string throws Error {...}

type testThrows = typeof testThrows;
//   ^? () => string throws Error

function testPromiseThrows(): Promise<string> throws Error {...}

type testPromiseThrows = typeof testPromiseThrows;
//   ^? () => Promise<string> throws Error

async function testAsync(): Promise<String> throws Error {...}
//                                          ^^^^^^^^^^^^
// Error: async function signatures can't specify throws as any awaited Promises that reject
// or any thing thrown within its body causes it to return Promise.reject(<thrown/rejected value>)
// rather than throwing.

Getters/Setters can throw, how do we handle that?
Because Getters/Setters can throw, it might be helpful to think of throws as a type modifier rather than only something that functions can do.
type stringOrThrowsError = string throws Error;

let a: string | undefined;

const o = {
    get value() {
        if (a == null) {
            throw new Error('a is not a string');
        }

        return a;
    }

     set value(val: string | undefined) {
        if (val == null) {
            throw new Error('cannot set val to a because val is not a string');
        }

        return a = val;
    }
}

type o = typeof o;
//   ^? { value: string throws Error }

function doSomething(v:  { value: string }) {...}

// compiler option strictThrows: false
doSomething(o); // ok

// compiler option strictThrows: true
doSomething(o);
//          ^
// Error type `{ value: string throws Error }` is not assignable to type `{ value: string throws never }`
// because type `Error` is not assignable to type `never`

How throws is inferred.
The thrown type can be inferred in two ways depending on a new compiler option strictThrows: boolean. The first way is to look at the type of the value thrown in a throw statement. The second way is to take the union of all thrown types from functions called within a the function being inferred (this does not apply if the compiler option strictThrows is set to true).
function mayThrowError(shouldThrow: boolean) {
    if (shouldThrow) throw new Error("message");
}

type mayThrowError = typeof mayThrowError;
//   ^? (shouldThrow: boolean) => void throws Error

function mayThrowString(shouldThrow: boolean) {
    if (shouldThrow) throw "my error" as const;
}

type mayThrowString = typeof mayThrowString;
//   ^? (shouldThrow: boolean) => void throws 'my error'

// compiler option strictThrows: false
function test1() {
    mayThrowError(true); // allowed
    mayThrowString(true); // allowed
}

type test1 = typeof test1;
//   ^? () => void throws Error | 'my error'

// compiler option strictThrows: true
function test2() {
    mayThrowError(true);
//  ^^^^^^^^^^^^^^^^^^^
// Error: unhandled possible thrown `Error`.
// Place this in a try catch or add `Error` to test2's throws signature.
    mayThrowString(true);
//  ^^^^^^^^^^^^^^^^^^^^
// Error: unhandled possible thrown `'my error'`.
// Place this in a try catch or add `'my error'` to test2's throws signature.
}

type test2 = typeof test2;
//   ^? () => void throws never

// asserts should infer throws even if compiler option strictThrows: true
function assertString(str: unknown): asserts str is string {
    if (typeof str !== "string") {
        throw new TypeError(`Expected a string but got a ${typeof str}`);
    }
}

type assertString = typeof assertString;
//   ^? (str: unknown) => asserts str is string throws TypeError

How catch(e) is inferred in non-async functions.
In non-async function the catch(e) is inferred as a union of the thrown type of any functions called, and any throw statements within the associated try block.
function doesNotThrow(): void {...};

try {
    doesNotThrow();
} catch (e) {
//       ^? unknown
}

function doesThrowError(): void throws Error;

try {
    doesThrowError();
    throw 'my error' as const
} catch (e) {
//       ^? Error | 'my error'
}

Working with throws in generics and conditionals.
When restricting a generic type or in conditional types with extends, if compiler option strictThrows is false and throws is left out, it is treated as if it was set to throws any. If compiler option strictThrows is true and throws is left out, it is treated as if it was set to throws never.
// helpful utility type to inspect the thrown type
type Throws<T> = T extends (...args: any[]) => any throws infer K ? K : never;

function square(num: number): number {...}
function squareThrows(num: number): number throws Error {...}

function wrap<T extends (...args: any) => any>(func: T): T {...}

wrap(square); // ok
// compiler option strictThrows: false
wrap(squareThrows); // ok

// compiler option strictThrows: true
wrap(squareThrows);
//   ^^^^^^^^^^^^
// Error: type `(num: number) => number throws Error` is not assignable to
// type `(...args: any) => any throws never`
// because type `Error` is not assignable to type `never`.

// this function throws what the pasted in mapper function throws.
// so if mapper doesn't throw then map doesn't as well and vice versa.
function map<T, M extends (item: T) => any throws any>(arr: T[], mapper: M): ReturnType<M> throws Throws<M>;

const nums: number[];

const mapped1 = map(nums, square);
//              ^? (arr: number[], mapper: (num: number) => number throws never) => number[] throws never

const mapped2 = map(nums, squareThrows);
//              ^? (arr: number[], mapper: (num: number) => number throws Error) => number[] throws Error

Updates to Promise types and async/await.
Because awaiting a Promise that rejects acts like throwing a value in an async function we need to capture the rejected type in the Promise to get the same benefits of the throws as non-async functions.
type ThenReturn<T> = T extends (v: any) => infer P extends Promise<any, any>
    ? P
    : T extends (v: any) => infer Return throws infer Thrown
    ? Promise<Return, Thrown>
    : never

interface Promise<T, R = never> {
    then<Resoled extends (value: T) => any throws any, Rejected extends (reason: R) => any throws any>(onresolved: Resoled, onrejected?: Rejected): ThenReturn<Resoled | Rejected>

    catch<Rejected extends (reason: R) => any throws any>(onrejected?: Rejected): ThenReturn<Rejected>

    finally(onfinally?: (() => void) | null | undefined): Promise<T, R>
}

interface PromiseConstructor {
    new <T, R = never>(cb: (resolve: (value: T) => void, reject?: (reason: R) => void) => void): Promise<T, R>
}

How this effects async/await.
Async functions are a bit more complicated. An async function returns a rejected Promise when one of the following occurs: it executes a throw statement within its body, it calls a non-async function that throws, or it awaits a promise that rejects.
function throwsString(): void throws 'thrown error';
function neverRejects(): Promise<string>;
function rejectsWithError(): Promise<string, Error>;
function rejectsWithString(): Promise<string, "rejected promise">;

// Compiler option strictThrows: false
async function test1() {
    throwsString(); // ok
    await neverRejects(); // ok
    await rejectsWithError(); // ok
    await rejectsWithString(); // ok
}

type test1 = typeof test1;
//   ^? () => Promise<void, Error | 'rejected promise' | 'thrown error'> throws never

// Compiler option strictThrows: true
async function test2() {
    throwsString();
//  ^^^^^^^^^^^^^^
// Error: unhandled possible thrown `'thrown error'`
    await neverRejects(); // ok
    await rejectsWithError();
//  ^^^^^^^^^^^^^^^^^^^^^^^^
// Error: unhandled possible thrown `Error`
    await rejectsWithString();
//  ^^^^^^^^^^^^^^^^^^^^^^^^^
// Error: unhandled possible thrown `'rejected promise'`
}

type test2 = typeof test2;
//   ^? () => Promise<void, never> throws never

async function test3(): Promise<void, Error | 'thrown error'> {
    throwsString(); // ok as test3's throws signature allows it
    await neverRejects(); // ok as this never rejects
    await rejectsWithError(); // ok as test3's throws signature allows it
    await rejectsWithString();
//  ^^^^^^^^^^^^^^^^^^^^^^^^^
// Error: unhandled possible thrown `'rejected promise'`
}

type test3 = typeof test3;
//   ^? () => Promise<void, Error | 'thrown error'> throws never

How catch(e) is inferred in async functions
In an async function the catch(e) is inferred the same as non-async functions with one addition. The inferred value is a union of the thrown type of any non-async functions called, throw statements, and the rejected reason of any awaited Promises within the associated try block.
function throwsString(): void throws 'thrown error';
function neverRejects(): Promise<string>;
function rejectsWithError(): Promise<string, Error>;
function rejectsWithString(): Promise<string, "rejected promise">;

async function test() {
    try {
        throwsString(); // might throw `'thrown error'`
        await neverRejects(); // ok never throws
        rejectsWithError(); // ok not awaited
        await rejectsWithString(); // might throw `'rejected promise'`
    } catch (e) {
//           ^? 'thrown error' | 'rejected promise'
    }
}

type test = typeof test;
//   ^? () => Promise<void, never> throws never

Duplicate of #13219.

I don't think there's much to work out in terms of how this would work, it's more a matter of whether. The linked issue is the place for discussion there.


Pt br leofig rj

Updated intents: _common.yaml, light_HassTurnOn.yaml, light_HassTurnOff.yaml, light_HassLightSet.yaml, fan_HassTurnOn.yaml and fan_HassTurnOff.yaml.
Updated responses: HassTurnOn.yaml and HassLightSet.yaml.
In pt-br.

Since there was no response at all, I'm declaring this PR stale and closing it.
Feel free to re-open this PR when you feel like that is the appropriate thing to do.
../Frenck


Boosting vs Ridge regrssion comparison

@christianbrodbeck what do we do with trftools?

Nevermind @christianbrodbeck, took care of trftools.

Thanks!


Use secrets.choice over random.choice

What was wrong?
Use of random.choice when we now have the better option of secrets.choice
How was it fixed?
Changed to use secrets.choice
Cute Animal Picture

This code is going away soon anyways, closing.


Assign to properties with explicit self in encode(to encoder: any Encoder)

Motivation
The generated encode(to encoder: any Encoder) assigns to properties without using explicit self. This is a problem because it can produce conflicts with the local variables created in the function, e.g. the encoding container, which will then fail to compile for schemas with properties named container, as found in https://github.com/apple/swift-openapi-generator/issues/695.
Modifications

Assign to properties with explicit self in encode(to encoder: any Encoder)

Test Plan

Update the reference tests.

@simonjbeaumont it seems to be working on my project with this change, sadly I didn't know what updates I should make for the snippet tests 😕. I you have any insight on this that would be helpful 🙏 .

@Dragna thanks for taking the time to put the patch up. I think we raced on this one. There's another PR up which adds the relevant snippet and reference tests: #699.


OC Meeting Agenda 2023-02-07

Time 5pm (GMT) - See the time in your timezone

Chair – Tammy McClellan @tmcclell (Microsoft)
Vice-Chair – Chris Lloyd-Jones @Sealjay (Avanade)
Convener – Sean Mcilroy @seanmcilroy29  (GSF)

Roll Call
Please add 'Attended' to this issue during the meeting to denote attendance.
Any untracked attendees will be added by the GSF team below:
Agenda

[x] Welcome our new Chair and Vice-Chair.
[x] Asim: Discuss repository clean-up project including renaming, permissioning, proposed deletions and mandatory meta information to be added to every repo's readme. https://github.com/Green-Software-Foundation/ops-admin/issues/146
[x] Asim: Discuss project proposal template as per https://github.com/Green-Software-Foundation/oc/discussions/7
[x] Asim: Discuss change to have 3 co-chairs instead of 2 as per https://github.com/Green-Software-Foundation/oc/discussions/9
[x] Asim: Discuss PM hiring process.
[x] Asim: Discuss elections
[ ] Asim: OKR Tracking.
[ ] Sean: Budget Tracking.
[ ] CLJ: https://github.com/Green-Software-Foundation/oc/discussions/11

[ ] AOB
Decisions

[x] Asim: Motion to increase the time for this meeting to 1 hr to cover all the agenda items starting at 0900-1000 am PT / 1700 pm to 1800 pm UTC.

Actions

[ ] @jawache: For the next meeting create package of changes to show how to update the charter for the 3 chairs.
[ ] @jawache: Change next meeting to 1hr long starting at 4:30 GMT

Attended

Attended! Woohoo!

attended :)

Attended, good banter this meeting

Attended

Attended, good banter this meeting

Memorialized in the recording lol

attended

Agree to change meeting to 1hr 4:30pm to 5:30 pm GMT

Agreed


Generate Invoices

Is your feature request related to a problem? Please describe.
Idea :

add thru a parameter page personal info such as SIRET / IBAN
Add a button to create the invoice at the end of each month line item
allow on the parameter page to load a custom html template for invoice

Describe the solution you'd like

That's just global ideas to improve this app

Hello Keirodev,
Thanks for your idea!
This feature is really interesting and I'm going to start to think how to implement it.
I keep this ticket open. I'm going to put new information soon.
Have a nice day!


fix travis build timeout error

Proposed changes:
Many of the past travis tests failed because this download:
wget --quiet -P /tmp/cached/ https://s3-eu-west-1.amazonaws.com/mitie/total_word_feature_extractor.dat

took longer than the standard 10 minute timeout.
This PR precedes it with the travis_wait function which doubles the timout to 20 minutes according to the docs.
Status (please check what you already did):

[ ] made PR ready for code review
[ ] added some tests for the functionality
[ ] updated the documentation
[ ] updated the changelog

related to #1677
But after seeing in that issue that even sometimes a normal curl on your aws timeouts I'm unsure whether this pr actually fixes the timeout reliably or there is a problem with your aws.

Hi @mauricedoepke thanks for the suggestion, but yeah i'm not entirely sure that's the best way to fix it. @tmbo what are your thoughts on this?

Thanks a lot, but I doubt this is an issue with AWS more likely travis. We'll move away from travis soonish in any case - but in the meantime this might help for some builds :+1:


Check if commenting out "ini_rules.apply_rules_on_ini_cst(ini_cst)" in convert.py and some other lines results in outputted mod INI files being identical

Done: b1d94118af998bf329ea32f2f75239b04ce73aa7

This seems to be identical to issue #121


Private Key Confusion

Atto only works with seeds. To test something I threw a private key for a specific address at it, and instead of errors, it generates a random address (which is not the one to the private key). I'm concerned this behavior will cause people to lose funds eventually.
Any way to fix this, or to get it working with private keys properly?

Oh, that's not good, thanks for the report. Right now atto just takes anything hexadecimal and uses it as the seed. I could at least verify that the length of the seed is correct.
How did the private key look? Was it also just 64 hexadecimal digits? In that case I'm afraid we would be out of luck; it's impossible to distinguish a seed from a private key, if both are represented as 64 hexadecimal digits. A seed is completely random and a private key is a hash, which would also look random to atto - there is no "magic byte" I could check for to see if it's a seed or key.

* Account private key
This is also a 32 byte value, usually represented as a 64 character, uppercase hexadecimal string(0-9A-F). It can either be random (an ad-hoc key) or derived from a seed, as described above. This is what represents control of a specific account on the ledger. If you know or can know the private key of someone's account, you can transact as if you own that account.

Looks like it was done this way for ease of use. You can input a private key into a wallet application as a normal seed, and have access to that index id within the seed as you would if you had the entire seed.

But if I take the private key and put it into nault.cc as a seed I get the same address as atto.

I cannot reproduce this. If I go to https://nault.cc/configure-wallet > "Import Seed" and enter 102d80c52e9c4fe0a066e1e9b960d18dffdd0a4efa6328f04644d3cc066f60d9 as the seed I end up with an account (index 0) which has the address nano_3wf47wd6unwughm4xui1ohaqegaws6azyucsu6uc4rxd7saesnwizjtebuw6.
The same thing happens with https://nanoo.tools/key-address-seed-converter.
Thus atto behaves exactly like the other wallets. None of them recognize that the private key is not a normal seed. I think this is because it's technically impossible to differentiate a seed and a private key.

If I go to https://nault.cc/configure-wallet > "Import Seed" and enter 102d80c52e9c4fe0a066e1e9b960d18dffdd0a4efa6328f04644d3cc066f60d9 as the seed I end up with an account (index 0) which has the address nano_3wf47wd6unwughm4xui1ohaqegaws6azyucsu6uc4rxd7saesnwizjtebuw6.

This is the error, though. This private key is not a seed however nault is treating it as one (because as you said there's no way to differentiate between them), and importing it as a seed is very confusing. To get to the funds, you wouldn't use your own seed to access the funds, as you would expect. You would need to extract that specific private key from the account index you did before and use it as a seed like you would opening a new wallet with a new seed. Using your main seed there would be no way for you to know under which account index the funds are. However, if you import the key, as a private key using nault.cc, it works as intended. You have access to only 1 wallet address--which is the intended behavior.
To put this another way, importing the private key as a private key under nault, produces an address of nano_1c6o6pdcipwb744i4pb64gu5oaneeugmbihn1yni8f1cyn3n1t3untgthsdr which is intended. Importing the private key as a seed produces an address of nano_3wf47wd6unwughm4xui1ohaqegaws6azyucsu6uc4rxd7saesnwizjtebuw6 which is a perfectly valid NANO address, but it will NOT be an address contained in the original seed where the private key came from. You're essentially using an accounts private key from SEED1 as a new seed (SEED2) which will give you 4.2 billion more addresses instead of just the 1, as intended.
Perplexing issue and it seems to be a fault with NANO, not atto. However, considering the differences, and it's possible to import the private key as a private key, I was wondering if you were interested in adding this functionality to atto. It would be highly useful.
Pass the key as you would a seed and notify atto that it's a key, and not a seed;
> echo %key% | atto -k a
> nano_1c6o6pdcipwb744i4pb64gu5oaneeugmbihn1yni8f1cyn3n1t3untgthsdr

[...] import the private key as a private key, I was wondering if you were interested in adding this functionality to atto. It would be highly useful.

Could you elaborate a little bit? In which scenarios would this be useful to you? What could you achieve with a private key export/import, that you couldn't achieve with a seed export/import?
When designing atto I had explicitly decided not to show private keys to the user to keep things simpler. It seems to me like a seed is more useful (because it can have multiple accounts). It also seems to me like seeds are what most wallets use when exporting and importing wallets.
I'm currently not inclined to add private key support to atto, but if you can show me some compelling use case for this feature, I might ponder the idea a little more.

Nothing incredibly compelling, unfortunately. I had several ideas which would allow a user (or business) to compartmentalize transactions and funds to create microservices using Go and atto to watch specific private keys for new transactions. Then, if anything is compromised it's going to be a single private key for a single index within a seed, instead of the entire seed.

I am going to close this ticket for now. I don't want to change atto for some use case that no one is actually invested in right now.
Besides that: It's true that I tried to design atto in a way that it could be used for different kinds of scenarios and even in small scripts, but my goal is not to provide a tool for implementing advanced business logic. My intention is to provide a simple wallet for people who like the command line. If someone wants to do something "unusual", I think it's better to take a little time and write a custom wallet/tool for that. For some scenarios the atto library might even help with that.


Added Countdown Timer program #320

Description
This is a simple python program which can be used for countdown.
In this user is required to input any number in seconds and then it will automatically count to zero(0) seconds
Type of change
Choosing one or more options from the following as per the nature of your Pull request.
NOTE: Check boxes using [x]

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Documentation Update

Checklist:

[x] I have named my files and folder, according to this project's guidelines.
[x] My code follows the style guidelines of this project.
[x] My Pull Request has a descriptive title. (not a vague title like Update index.md)
[x] I have commented on my code, particularly in hard-to-understand areas.
[x] I have created a helpful and easy to understand README.md, with problem description and my name.
[x] I have included a requirements.txt file (if external libraries are required.)
[x] My changes do not produce any warnings.
[x] I have starred this repository.
[x] I have added a working sample/screenshot of the script.
[x] I have checked for trailing spaces in file names and none have them.

closes #320

Hey @pratik-choudhari , please review

@uddeshyatyagi Instead of giving a feedback in terminal. Use pygame and play a alarm clock sound.

@pratik-choudhari clock sound added


Add PGP badge to readme linking to Keybase proofs

Thought this looked cool.

Good idea!
Why is this one much longer than the ones suggested in https://github.com/keybase/keybase-issues/issues/849#issuecomment-198513202 and https://github.com/badges/shields/issues/1299 ?

And vote this up: https://github.com/amio/badgen-service/issues/140

Why is this one much longer?

32-bit PGP fingerprints are trivial to brute force so I used the 64-bit PGP fingerprint.

Note to self: Update to https://badgen.net, when this is merged: https://github.com/amio/badgen-service/pull/141


Added move tab to new window

Same as right clicking your current tab and selecting "Move to New Window".

Looks good. Do you think this command should have no bindings by default?