[All Hosts](shared runtime): Update and move shared runtime articles for PPT support

This moves several articles concerning the shared JavaScript runtime from the Excel node to the Develop node. This is to support that PowerPoint will now be able to use shared runtime as well (it is not just an Excel thing.) Also rewrote content to be more about Office Add-ins, and not specifically Excel.

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

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/excel/configure-your-add-in-to-use-a-shared-runtime.md
:white_check_mark:Succeeded
View

docs/excel/custom-functions-shared-overview.md
:white_check_mark:Succeeded
View

docs/excel/run-code-on-document-open.md
:white_check_mark:Succeeded
View

docs/excel/show-hide-add-in.md
:white_check_mark:Succeeded
View

docs/includes/shared-runtime-requirements-note.md
:white_check_mark:Succeeded
View

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

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

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/excel/configure-your-add-in-to-use-a-shared-runtime.md
:white_check_mark:Succeeded
View

docs/excel/custom-functions-shared-overview.md
:white_check_mark:Succeeded
View

docs/excel/run-code-on-document-open.md
:white_check_mark:Succeeded
View

docs/excel/show-hide-add-in.md
:white_check_mark:Succeeded
View

docs/includes/shared-runtime-requirements-note.md
:white_check_mark:Succeeded
View

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

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

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/excel/configure-your-add-in-to-use-a-shared-runtime.md
:white_check_mark:Succeeded
View

docs/excel/custom-functions-shared-overview.md
:white_check_mark:Succeeded
View

docs/excel/run-code-on-document-open.md
:white_check_mark:Succeeded
View

docs/excel/show-hide-add-in.md
:white_check_mark:Succeeded
View

docs/includes/shared-runtime-requirements-note.md
:white_check_mark:Succeeded
View

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

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

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/excel/configure-your-add-in-to-use-a-shared-runtime.md
:white_check_mark:Succeeded
View

docs/excel/custom-functions-shared-overview.md
:white_check_mark:Succeeded
View

docs/excel/run-code-on-document-open.md
:white_check_mark:Succeeded
View

docs/excel/show-hide-add-in.md
:white_check_mark:Succeeded
View

docs/images/custom-functions-in-browser-runtime.png
:white_check_mark:Succeeded
View

docs/includes/shared-runtime-requirements-note.md
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 4b2ae04:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/develop/configure-your-add-in-to-use-a-shared-runtime.md
:warning:Warning
View
Details

docs/develop/run-code-on-document-open.md
:warning:Warning
View
Details

docs/reference/manifest/runtimes.md
:warning:Warning
View
Details

docs/excel/custom-functions-overview.md
:warning:Warning
View
Details

docs/reference/manifest/runtime.md
:warning:Warning
View
Details

docs/design/contextual-tabs.md
:warning:Warning
View
Details

docs/includes/note-requires-shared-runtime.md
:warning:Warning
View
Details

docs/includes/shared-runtime-note.md
:warning:Warning
View
Details

docs/tutorials/excel-tutorial-create-custom-functions.md
:warning:Warning
View
Details

docs/design/keyboard-shortcuts.md
:warning:Warning
View
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/develop/show-hide-add-in.md
:white_check_mark:Succeeded
View

docs/excel/configure-your-add-in-to-use-a-shared-runtime.md
:white_check_mark:Succeeded

docs/excel/custom-functions-shared-overview.md
:white_check_mark:Succeeded
View

docs/excel/run-code-on-document-open.md
:white_check_mark:Succeeded
View

docs/images/custom-functions-in-browser-runtime.png
:white_check_mark:Succeeded
View

docs/includes/shared-runtime-requirements-note.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

docs/develop/configure-your-add-in-to-use-a-shared-runtime.md

Line 219, Column 3: [Warning-file-not-found] Invalid file link: 'call-excel-apis-from-custom-function.md'.

docs/develop/run-code-on-document-open.md

Line 105, Column 3: [Warning-file-not-found] Invalid file link: 'excel-add-ins-events.md'.

docs/reference/manifest/runtimes.md

Line 14, Column 127: [Warning-file-not-found] Invalid file link: '../../excel/configure-your-add-in-to-use-a-shared-runtime.md'.

docs/excel/custom-functions-overview.md

Line 73, Column 217: [Warning-file-not-found] Invalid file link: 'configure-your-add-in-to-use-a-shared-runtime.md'.

docs/reference/manifest/runtime.md

Line 12, Column 127: [Warning-file-not-found] Invalid file link: '../../excel/configure-your-add-in-to-use-a-shared-runtime.md'.

docs/design/contextual-tabs.md

Line 50, Column 105: [Warning-file-not-found] Invalid file link: '../excel/configure-your-add-in-to-use-a-shared-runtime.md'.

docs/includes/note-requires-shared-runtime.md

Line 2, Column 114: [Warning-file-not-found] Invalid file link: '../excel/configure-your-add-in-to-use-a-shared-runtime.md'.

docs/includes/shared-runtime-note.md

Line 2, Column 107: [Warning-file-not-found] Invalid file link: '../excel/configure-your-add-in-to-use-a-shared-runtime.md'.

docs/tutorials/excel-tutorial-create-custom-functions.md

Line 246, Column 3: [Warning-file-not-found] Invalid file link: '../excel/configure-your-add-in-to-use-a-shared-runtime.md'.

docs/design/keyboard-shortcuts.md

Line 29, Column 104: [Warning-file-not-found] Invalid file link: '../excel/configure-your-add-in-to-use-a-shared-runtime.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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 07ba37f:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/develop/configure-your-add-in-to-use-a-shared-runtime.md
:warning:Warning
View
Details

docs/develop/run-code-on-document-open.md
:warning:Warning
View
Details

docs/reference/manifest/runtime.md
:warning:Warning
View
Details

docs/reference/manifest/runtimes.md
:warning:Warning
View
Details

docs/tutorials/excel-tutorial-create-custom-functions.md
:warning:Warning
View
Details

docs/design/keyboard-shortcuts.md
:warning:Warning
View
Details

docs/excel/custom-functions-overview.md
:warning:Warning
View
Details

docs/includes/shared-runtime-note.md
:warning:Warning
View
Details

docs/design/contextual-tabs.md
:warning:Warning
View
Details

docs/includes/note-requires-shared-runtime.md
:warning:Warning
View
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/develop/show-hide-add-in.md
:white_check_mark:Succeeded
View

docs/excel/configure-your-add-in-to-use-a-shared-runtime.md
:white_check_mark:Succeeded

docs/excel/custom-functions-shared-overview.md
:white_check_mark:Succeeded
View

docs/excel/run-code-on-document-open.md
:white_check_mark:Succeeded
View

docs/images/custom-functions-in-browser-runtime.png
:white_check_mark:Succeeded
View

docs/includes/shared-runtime-requirements-note.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

docs/develop/configure-your-add-in-to-use-a-shared-runtime.md

Line 219, Column 3: [Warning-file-not-found] Invalid file link: 'call-excel-apis-from-custom-function.md'.

docs/develop/run-code-on-document-open.md

Line 105, Column 3: [Warning-file-not-found] Invalid file link: 'excel-add-ins-events.md'.

docs/reference/manifest/runtime.md

Line 12, Column 127: [Warning-file-not-found] Invalid file link: '../../excel/configure-your-add-in-to-use-a-shared-runtime.md'.

docs/reference/manifest/runtimes.md

Line 14, Column 127: [Warning-file-not-found] Invalid file link: '../../excel/configure-your-add-in-to-use-a-shared-runtime.md'.

docs/tutorials/excel-tutorial-create-custom-functions.md

Line 246, Column 3: [Warning-file-not-found] Invalid file link: '../excel/configure-your-add-in-to-use-a-shared-runtime.md'.

docs/design/keyboard-shortcuts.md

Line 29, Column 104: [Warning-file-not-found] Invalid file link: '../excel/configure-your-add-in-to-use-a-shared-runtime.md'.

docs/excel/custom-functions-overview.md

Line 73, Column 217: [Warning-file-not-found] Invalid file link: 'configure-your-add-in-to-use-a-shared-runtime.md'.

docs/includes/shared-runtime-note.md

Line 2, Column 107: [Warning-file-not-found] Invalid file link: '../excel/configure-your-add-in-to-use-a-shared-runtime.md'.

docs/design/contextual-tabs.md

Line 50, Column 105: [Warning-file-not-found] Invalid file link: '../excel/configure-your-add-in-to-use-a-shared-runtime.md'.

docs/includes/note-requires-shared-runtime.md

Line 2, Column 114: [Warning-file-not-found] Invalid file link: '../excel/configure-your-add-in-to-use-a-shared-runtime.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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 0fed943:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/design/keyboard-shortcuts.md
:warning:Warning
View
Details

docs/reference/manifest/runtime.md
:warning:Warning
View
Details

docs/tutorials/excel-tutorial-create-custom-functions.md
:warning:Warning
View
Details

docs/includes/note-requires-shared-runtime.md
:warning:Warning
View
Details

docs/includes/shared-runtime-note.md
:warning:Warning
View
Details

docs/excel/custom-functions-overview.md
:warning:Warning
View
Details

docs/design/contextual-tabs.md
:warning:Warning
View
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/develop/configure-your-add-in-to-use-a-shared-runtime.md
:white_check_mark:Succeeded
View

docs/develop/run-code-on-document-open.md
:white_check_mark:Succeeded
View

docs/develop/show-hide-add-in.md
:white_check_mark:Succeeded
View

docs/excel/configure-your-add-in-to-use-a-shared-runtime.md
:white_check_mark:Succeeded

docs/excel/custom-functions-shared-overview.md
:white_check_mark:Succeeded
View

docs/excel/run-code-on-document-open.md
:white_check_mark:Succeeded
View

docs/images/custom-functions-in-browser-runtime.png
:white_check_mark:Succeeded
View

docs/includes/shared-runtime-requirements-note.md
:white_check_mark:Succeeded
View

docs/reference/manifest/runtimes.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

docs/design/keyboard-shortcuts.md

Line 29, Column 104: [Warning-file-not-found] Invalid file link: '../excel/configure-your-add-in-to-use-a-shared-runtime.md'.

docs/reference/manifest/runtime.md

Line 12, Column 127: [Warning-file-not-found] Invalid file link: '../../excel/configure-your-add-in-to-use-a-shared-runtime.md'.

docs/tutorials/excel-tutorial-create-custom-functions.md

Line 246, Column 3: [Warning-file-not-found] Invalid file link: '../excel/configure-your-add-in-to-use-a-shared-runtime.md'.

docs/includes/note-requires-shared-runtime.md

Line 2, Column 114: [Warning-file-not-found] Invalid file link: '../excel/configure-your-add-in-to-use-a-shared-runtime.md'.

docs/includes/shared-runtime-note.md

Line 2, Column 107: [Warning-file-not-found] Invalid file link: '../excel/configure-your-add-in-to-use-a-shared-runtime.md'.

docs/excel/custom-functions-overview.md

Line 73, Column 217: [Warning-file-not-found] Invalid file link: 'configure-your-add-in-to-use-a-shared-runtime.md'.

docs/design/contextual-tabs.md

Line 50, Column 105: [Warning-file-not-found] Invalid file link: '../excel/configure-your-add-in-to-use-a-shared-runtime.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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

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

File
Status
Preview URL
Details

docs/excel/custom-functions-overview.md
:warning:Warning
View
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/design/contextual-tabs.md
:white_check_mark:Succeeded
View

docs/design/keyboard-shortcuts.md
:white_check_mark:Succeeded
View

docs/develop/configure-your-add-in-to-use-a-shared-runtime.md
:white_check_mark:Succeeded
View

docs/develop/run-code-on-document-open.md
:white_check_mark:Succeeded
View

docs/develop/show-hide-add-in.md
:white_check_mark:Succeeded
View

docs/excel/configure-your-add-in-to-use-a-shared-runtime.md
:white_check_mark:Succeeded

docs/excel/custom-functions-shared-overview.md
:white_check_mark:Succeeded
View

docs/excel/run-code-on-document-open.md
:white_check_mark:Succeeded
View

docs/images/custom-functions-in-browser-runtime.png
:white_check_mark:Succeeded
View

docs/includes/note-requires-shared-runtime.md
:white_check_mark:Succeeded
View

docs/includes/shared-runtime-note.md
:white_check_mark:Succeeded
View

docs/includes/shared-runtime-requirements-note.md
:white_check_mark:Succeeded
View

docs/reference/manifest/runtime.md
:white_check_mark:Succeeded
View

docs/reference/manifest/runtimes.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

docs/tutorials/excel-tutorial-create-custom-functions.md
:white_check_mark:Succeeded
View

docs/excel/custom-functions-overview.md

Line 73, Column 217: [Warning-file-not-found] Invalid file link: 'configure-your-add-in-to-use-a-shared-runtime.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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

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

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/design/contextual-tabs.md
:white_check_mark:Succeeded
View

docs/design/keyboard-shortcuts.md
:white_check_mark:Succeeded
View

docs/develop/configure-your-add-in-to-use-a-shared-runtime.md
:white_check_mark:Succeeded
View

docs/develop/run-code-on-document-open.md
:white_check_mark:Succeeded
View

docs/develop/show-hide-add-in.md
:white_check_mark:Succeeded
View

docs/excel/configure-your-add-in-to-use-a-shared-runtime.md
:white_check_mark:Succeeded

docs/excel/custom-functions-overview.md
:white_check_mark:Succeeded
View

docs/excel/custom-functions-shared-overview.md
:white_check_mark:Succeeded
View

docs/excel/run-code-on-document-open.md
:white_check_mark:Succeeded
View

docs/images/custom-functions-in-browser-runtime.png
:white_check_mark:Succeeded
View

docs/includes/note-requires-shared-runtime.md
:white_check_mark:Succeeded
View

docs/includes/shared-runtime-note.md
:white_check_mark:Succeeded
View

docs/includes/shared-runtime-requirements-note.md
:white_check_mark:Succeeded
View

docs/reference/manifest/runtime.md
:white_check_mark:Succeeded
View

docs/reference/manifest/runtimes.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

docs/tutorials/excel-tutorial-create-custom-functions.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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

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

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/design/contextual-tabs.md
:white_check_mark:Succeeded
View

docs/design/keyboard-shortcuts.md
:white_check_mark:Succeeded
View

docs/develop/configure-your-add-in-to-use-a-shared-runtime.md
:white_check_mark:Succeeded
View

docs/develop/run-code-on-document-open.md
:white_check_mark:Succeeded
View

docs/develop/show-hide-add-in.md
:white_check_mark:Succeeded
View

docs/excel/configure-your-add-in-to-use-a-shared-runtime.md
:white_check_mark:Succeeded

docs/excel/custom-functions-overview.md
:white_check_mark:Succeeded
View

docs/excel/custom-functions-shared-overview.md
:white_check_mark:Succeeded
View

docs/excel/run-code-on-document-open.md
:white_check_mark:Succeeded
View

docs/images/custom-functions-in-browser-runtime.png
:white_check_mark:Succeeded
View

docs/includes/note-requires-shared-runtime.md
:white_check_mark:Succeeded
View

docs/includes/shared-runtime-note.md
:white_check_mark:Succeeded
View

docs/includes/shared-runtime-requirements-note.md
:white_check_mark:Succeeded
View

docs/reference/manifest/runtime.md
:white_check_mark:Succeeded
View

docs/reference/manifest/runtimes.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

docs/tutorials/excel-tutorial-create-custom-functions.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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

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

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/design/contextual-tabs.md
:white_check_mark:Succeeded
View

docs/design/keyboard-shortcuts.md
:white_check_mark:Succeeded
View

docs/develop/configure-your-add-in-to-use-a-shared-runtime.md
:white_check_mark:Succeeded
View

docs/develop/run-code-on-document-open.md
:white_check_mark:Succeeded
View

docs/develop/show-hide-add-in.md
:white_check_mark:Succeeded
View

docs/excel/configure-your-add-in-to-use-a-shared-runtime.md
:white_check_mark:Succeeded

docs/excel/custom-functions-overview.md
:white_check_mark:Succeeded
View

docs/excel/custom-functions-shared-overview.md
:white_check_mark:Succeeded
View

docs/excel/run-code-on-document-open.md
:white_check_mark:Succeeded
View

docs/images/custom-functions-in-browser-runtime.png
:white_check_mark:Succeeded
View

docs/includes/note-requires-shared-runtime.md
:white_check_mark:Succeeded
View

docs/includes/shared-runtime-note.md
:white_check_mark:Succeeded
View

docs/includes/shared-runtime-requirements-note.md
:white_check_mark:Succeeded
View

docs/reference/manifest/runtime.md
:white_check_mark:Succeeded
View

docs/reference/manifest/runtimes.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

docs/tutorials/excel-tutorial-create-custom-functions.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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 33033d7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/design/contextual-tabs.md
:white_check_mark:Succeeded
View

docs/design/keyboard-shortcuts.md
:white_check_mark:Succeeded
View

docs/develop/configure-your-add-in-to-use-a-shared-runtime.md
:white_check_mark:Succeeded
View

docs/develop/run-code-on-document-open.md
:white_check_mark:Succeeded
View

docs/develop/show-hide-add-in.md
:white_check_mark:Succeeded
View

docs/excel/configure-your-add-in-to-use-a-shared-runtime.md
:white_check_mark:Succeeded

docs/excel/custom-functions-overview.md
:white_check_mark:Succeeded
View

docs/excel/custom-functions-shared-overview.md
:white_check_mark:Succeeded
View

docs/excel/run-code-on-document-open.md
:white_check_mark:Succeeded
View

docs/images/custom-functions-in-browser-runtime.png
:white_check_mark:Succeeded
View

docs/includes/note-requires-shared-runtime.md
:white_check_mark:Succeeded
View

docs/includes/shared-runtime-note.md
:white_check_mark:Succeeded
View

docs/includes/shared-runtime-requirements-note.md
:white_check_mark:Succeeded
View

docs/reference/manifest/runtime.md
:white_check_mark:Succeeded
View

docs/reference/manifest/runtimes.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

docs/tutorials/excel-tutorial-create-custom-functions.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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 33033d7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/design/contextual-tabs.md
:white_check_mark:Succeeded
View

docs/design/keyboard-shortcuts.md
:white_check_mark:Succeeded
View

docs/develop/configure-your-add-in-to-use-a-shared-runtime.md
:white_check_mark:Succeeded
View

docs/develop/run-code-on-document-open.md
:white_check_mark:Succeeded
View

docs/develop/show-hide-add-in.md
:white_check_mark:Succeeded
View

docs/excel/configure-your-add-in-to-use-a-shared-runtime.md
:white_check_mark:Succeeded

docs/excel/custom-functions-overview.md
:white_check_mark:Succeeded
View

docs/excel/custom-functions-shared-overview.md
:white_check_mark:Succeeded
View

docs/excel/run-code-on-document-open.md
:white_check_mark:Succeeded
View

docs/images/custom-functions-in-browser-runtime.png
:white_check_mark:Succeeded
View

docs/includes/note-requires-shared-runtime.md
:white_check_mark:Succeeded
View

docs/includes/shared-runtime-note.md
:white_check_mark:Succeeded
View

docs/includes/shared-runtime-requirements-note.md
:white_check_mark:Succeeded
View

docs/reference/manifest/runtime.md
:white_check_mark:Succeeded
View

docs/reference/manifest/runtimes.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

docs/tutorials/excel-tutorial-create-custom-functions.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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 2339aea:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/design/contextual-tabs.md
:white_check_mark:Succeeded
View

docs/design/keyboard-shortcuts.md
:white_check_mark:Succeeded
View

docs/develop/configure-your-add-in-to-use-a-shared-runtime.md
:white_check_mark:Succeeded
View

docs/develop/run-code-on-document-open.md
:white_check_mark:Succeeded
View

docs/develop/show-hide-add-in.md
:white_check_mark:Succeeded
View

docs/excel/configure-your-add-in-to-use-a-shared-runtime.md
:white_check_mark:Succeeded

docs/excel/custom-functions-overview.md
:white_check_mark:Succeeded
View

docs/excel/custom-functions-shared-overview.md
:white_check_mark:Succeeded
View

docs/excel/run-code-on-document-open.md
:white_check_mark:Succeeded
View

docs/images/custom-functions-in-browser-runtime.png
:white_check_mark:Succeeded
View

docs/includes/note-requires-shared-runtime.md
:white_check_mark:Succeeded
View

docs/includes/shared-runtime-note.md
:white_check_mark:Succeeded
View

docs/includes/shared-runtime-requirements-note.md
:white_check_mark:Succeeded
View

docs/reference/manifest/runtime.md
:white_check_mark:Succeeded
View

docs/reference/manifest/runtimes.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

docs/tutorials/excel-tutorial-create-custom-functions.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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 2339aea:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/design/contextual-tabs.md
:white_check_mark:Succeeded
View

docs/design/keyboard-shortcuts.md
:white_check_mark:Succeeded
View

docs/develop/configure-your-add-in-to-use-a-shared-runtime.md
:white_check_mark:Succeeded
View

docs/develop/run-code-on-document-open.md
:white_check_mark:Succeeded
View

docs/develop/show-hide-add-in.md
:white_check_mark:Succeeded
View

docs/excel/configure-your-add-in-to-use-a-shared-runtime.md
:white_check_mark:Succeeded

docs/excel/custom-functions-overview.md
:white_check_mark:Succeeded
View

docs/excel/custom-functions-shared-overview.md
:white_check_mark:Succeeded
View

docs/excel/run-code-on-document-open.md
:white_check_mark:Succeeded
View

docs/images/custom-functions-in-browser-runtime.png
:white_check_mark:Succeeded
View

docs/includes/note-requires-shared-runtime.md
:white_check_mark:Succeeded
View

docs/includes/shared-runtime-note.md
:white_check_mark:Succeeded
View

docs/includes/shared-runtime-requirements-note.md
:white_check_mark:Succeeded
View

docs/reference/manifest/runtime.md
:white_check_mark:Succeeded
View

docs/reference/manifest/runtimes.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

docs/tutorials/excel-tutorial-create-custom-functions.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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


New face

Running through the endpoints on https://docs.puppet.com/pe/latest/nc_index.html
Considerations

Should it allow updates?

Existing puppet code would update
Mostly used for bootstrapping, not daemon code

Demoed for TSEs.  They provided some feedback:

Allow face to export all groups
Allow face to import all groups

NOTE: The hashify_group_array reorders the JSON response so that it is not useable as a request's payload.  An export action would have to not do this.  That is, this format won't work:
puppet node_manager groups --all --render-as json

Ditched the --all flag.  Refactored so if you don't supply an argument to the query, it will list all.  For example:

List all
puppet node_manager groups

List one
puppet node_manager groups my_group

Revamped some of the returns so querying a single value would return pretty JSON and query multiple values would return a list of keys.  Also added some better error handling based on HTTP codes.  PR lives here: https://github.com/WhatsARanjit/prosvcs-node_manager/pull/21

Merged.


Space Traveller's Hub (Feature/create app)

In this part of the project,

[x] I created a react app and installed dependencies for the project

@siddghosh108, please take time to review the work before I can merge it to dev branch.
Issue Link: https://github.com/lucy-sees/Space-Travellers-Hub/issues/1

Ready to merge


Set up application layout

Thanks to the great work of the design team, we've got some designs! So we should adjust the frontend application layout to account for that.
The Invision Prototype, which we should try to match, is here: https://projects.invisionapp.com/share/6757W6WFJ
For purposes of testing, you can go to http://localhost:3000/users/sign_up (the devise login pages).
This ticket has three components:

Editing the master layout partial in app/views/layouts/application.html.erb to match the top bar in InVision
Editing app/cases/index.html.erb to account for the change in the application layout (delayed until after sprint 1)
Gold medal: Where Sarah Caseworker appears in the Invision app, have that populate with either the results of current_user.name if a user is signed in or a link to the sign in page if not.

How should we incorporate a design review into this (or other) issues? Should we?

@mebates I'm 100% about doing a design review and iterating on layouts/frontend code. There's a lot of UX expertise and talent on this between you and @adinneen and I don't want to waste any of it.
Should we do it incrementally on individual components (such as the top bar) as they're rolled out, or should we start doing them after we have kind of the basic views and interactions from the InVision app turned into code?

Since design review is a bit of a broader question, I'm going to split it into a separate issue for further discussion, and rack the last bullet in the ticket in the current frontend PR I'm working on. Design review is an A++ flag and I want to make sure it doesn't get buried here.


Ability to provide void value in env variable override

I want to provide a void value for a particular environmental variable for a particular. This is not possible in Amplify Console UI because the value field is required:

What is the feasibility of providing a UI control to "nullify" the value in the override?

Hi @dmudro yes, env variables require some value. Could you provide a value of "null" and treat that as null in your app code?
Can you also explain your use case and we can consider a feature request for this. Thanks!

Yes the "null" workaround is pretty much what we are doing. It's not a real null obviously but stringify'd as env vars are always strings.
The use case is feature toggling. Let's say I want to enable a particular feature based on a presence of an ENV VAR, such as API_URL=https://api.example.com/v1 in all branches but master / production.
So now to disable the new api dependent feature in production I have to define API_URL=null override and then do string comparison process.env.API_URL === null down in the app. Kinda works, just not as elegant. On that note, it could be whatever arbitrary value, e. g. API_URL=0 and then process.env.API_URL === 0 or parseInt(process.env.API.URL, 10).
Using standard env var mechanism without AWS Amplify Console I'd just set it to nothing:
API_URL=

I could also set up a brand new env var just to do the feature toggling but that's just adding more noise to already slightly cumbersome env vars management UI.
While this feature request asks for eventually considering allowing empty values, I don't think
removing the required check from the field is the best solution; perhaps something more explicit in the Actions dropdown or other UI control could do the trick.
Or maybe the whole env vars management is ready for an overhaul ;)


support instance tags and include relevant specs

What is this change about?
The change allows to configure instance group specific tags, by allowing the user to include tags under <instance_group> -> env -> bosh -> tags in the manifest.
These tags can be configured as follows:
instance_groups:
- name: <instance_group>
  env:
    bosh:
     .
     .
      tags:
        tag1: value1
        tag2: value2

The deployment tags and the tags from the runtime config are also merged.
These tags can be useful under many circumstances, for example, in a large organisation, it makes identifying teams responsible for different instances easier. Also, This feature removes the necessity of including tags for the entire deployment when such tags aren't needed for all the involved instance groups.
What tests have you run against this PR?
bosh-director unit tests, dev-release testing on development environments
How should this change be described in bosh release notes?
Support instance group specific tags.
Does this PR introduce a breaking change?
No breaking change, since this PR just supports additional functionality of supporting instance tags.
Tag your pair, your PM, and/or team!
@mvach @a-hassanin

@ansh-SAP could you please sign the CLI and also add information about why this change is useful.

@anshrupani one of the commits is with @ansh-SAP which didn't sign the CLA. Could you fix this and also add information about why this change is useful.

Thanks for pointing out!

could you squash these commits?

Closing in favour of https://github.com/cloudfoundry/bosh/pull/2448


light need to be rebuilt in night in 0.9.15

CARLA version: 0.9.15
Platform/OS:windows11
Problem you have experienced: when time change to night, not all the light is on. The UE4 editor appears"light need to be rebuilt",and light behavior is different from that in 0.9.14
0.9.14:

0.9.15：

the method in this https://www.youtube.com/watch?v=iPN2hWzfmP8&ab_channel=qubodupDev doesn't work. The problem still exists. When I choose only to rebuild lighting, this instruction appears

the light need to be rebuilt happens when time changes to night. And I build Carla on another computer, the problem still exists

Hello, and thanks for your time. I've fixed the problem you say about the museum emissive textures, it will be on the next release.
About the lights needs to be rebuilt, this message appears every time you move anything static on the scene, but since we're using a dynamic light, this is not necessary.
Thanks again for your help finding this problem!

Hello, and thanks for your time. I've fixed the problem you say about the museum emissive textures, it will be on the next release.
About the lights needs to be rebuilt, this message appears every time you move anything static on the scene, but since we're using a dynamic light, this is not necessary.
Thanks again for your help finding this problem!

Thanks for your reply, but I think not only museum light is different from 0.9.14. Many lights in building also different. Just see the photo I post, the building behind seems behaves differently. In my opiniom  Maybe 13610 light not open, same as the message light need to be rebuilt.
And response to your explanation about light needs to be rebuilt problem, I run the same script to generate image. They all have world.unload_map_layer(carla.MapLayer.ParkedVehicles). Maybe this means removing static on the scene? But when I run the script in 0.9.14, the message don't appear. It only happens in 0.9.15

Should I change the light from fix to movable to make all the lights on ?

Reference in ne
Should I change the light from fix to movable to make all the lights on ?

Is there any way to change the source about emissive textures same from 0.9.14

Hello, I'm still looking at this, since moving between versions take some time, if you think that the problem is the material, you can create a simple material with emissive texture and test with it.
I'll update you later, thanks for your time!

I have been testing the error and I cannot reproduce it, the lights look fine to me. The source of the emissive textures is the same as version 9.14, so it shouldn't be a problem.
It may be that in the next release your problem will disappear.
Thanks for your time.


Test Windows/Linux support

Willing to Windows Test
Win10 Pro - Build 18362 Currently

I can test on Windows.

Thanks, all... Linux support is solid and Windows is a WIP you can follow in this issue - getting pretty close to done now.  Going to go ahead and close this one.


Fix broken public_ip output

This is a cherry-pick of https://github.com/maartenvanderhoef/terraform-aws-ec2-instance/commit/6dab63992388e106c6969acdf510906700769a67
It has been extended to include the README being rebuilt.
See also #46

/codefresh run test


TES should always upload stdout and stderr

Currently, when a TES task succeeds, stdout and stderr are not uploaded.  This might be a Batch config setting.
It's expected that stdout and stderr are always uploaded.

fixed via #322

This appears to have regressed.
I have a partial fix ready, which I'll provide today.

I'm reopening a more appropriate issue for this regression.


support python 3.10

Codecov Report

Merging #86 (cd0cec4) into main (7a0d4bd) will decrease coverage by 0.06%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #86      +/-   ##
==========================================
- Coverage   90.80%   90.74%   -0.07%
==========================================
  Files          33       33
  Lines        3665     3641      -24
==========================================
- Hits         3328     3304      -24
  Misses        337      337

Impacted Files
Coverage Δ

megfile/pathlike.py
88.51% <100.00%> (-0.16%)
:arrow_down:

megfile/utils/mutex.py
87.69% <0.00%> (-0.72%)
:arrow_down:

megfile/lib/s3_prefetch_reader.py
90.94% <0.00%> (-0.15%)
:arrow_down:

megfile/s3.py
91.19% <0.00%> (-0.13%)
:arrow_down:

megfile/lib/shadow_handler.py
94.44% <0.00%> (-0.11%)
:arrow_down:

megfile/errors.py
85.22% <0.00%> (-0.09%)
:arrow_down:

megfile/lib/combine_reader.py
94.89% <0.00%> (-0.06%)
:arrow_down:

megfile/cli.py
97.82% <0.00%> (-0.05%)
:arrow_down:

megfile/lib/s3_buffered_writer.py
98.37% <0.00%> (-0.04%)
:arrow_down:

... and 4 more

Continue to review full report at Codecov.

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


test the webscrape

scrape.py
make sure its creating the dictionary where each key is the name of an emoji
and the value is the link to the img source

5f64949967f92acc01bc95f6778487168a9ac507
need to replace ':' so that emoji names can be use as file names. minor


[FEATURE REQUEST] Add onPredictionsChanged to access the predictions returned by Google

Hi! 👋
Firstly, thanks for your work on this project! 🙂
Today I used patch-package to patch<EMAIL_ADDRESS>for the project I'm working on.
I wanted to be able to access to the results of the predictions so I could update my design accordingly.
Here is the diff that solved my problem:
diff --git a/node_modules/react-native-google-places-autocomplete/GooglePlacesAutocomplete.d.ts b/node_modules/react-native-google-places-autocomplete/GooglePlacesAutocomplete.d.ts
index 1fbd5f9..b9aca76 100644
--- a/node_modules/react-native-google-places-autocomplete/GooglePlacesAutocomplete.d.ts
+++ b/node_modules/react-native-google-places-autocomplete/GooglePlacesAutocomplete.d.ts
@@ -406,6 +406,7 @@ interface GooglePlacesAutocompleteProps {
   onNotFound?: () => void;
   onPress?: (data: GooglePlaceData, detail: GooglePlaceDetail | null) => void;
   onTimeout?: () => void;
+  onPredictionsChanged?: (predictions: GooglePlaceData[]) => void;
   placeholder: string;
   predefinedPlaces?: Place[];
   predefinedPlacesAlwaysVisible?: boolean;
diff --git a/node_modules/react-native-google-places-autocomplete/GooglePlacesAutocomplete.js b/node_modules/react-native-google-places-autocomplete/GooglePlacesAutocomplete.js
index cd03253..ac7f133 100644
--- a/node_modules/react-native-google-places-autocomplete/GooglePlacesAutocomplete.js
+++ b/node_modules/react-native-google-places-autocomplete/GooglePlacesAutocomplete.js
@@ -134,12 +134,20 @@ export const GooglePlacesAutocomplete = forwardRef((props, ref) => {
   };

   const [stateText, setStateText] = useState('');
-  const [dataSource, setDataSource] = useState(buildRowsFromResults([]));
+  const [dataSource, setDataSourceState] = useState(buildRowsFromResults([]));
   const [listViewDisplayed, setListViewDisplayed] = useState(
     props.listViewDisplayed === 'auto' ? false : props.listViewDisplayed,
   );
   const [url] = useState(getRequestUrl(props.requestUrl));

+  const setDataSource = (dataSource) => {
+    if (props.onPredictionsChanged) {
+      props.onPredictionsChanged(dataSource)
+    }
+
+    setDataSourceState(dataSource)
+  };
+
   const inputRef = useRef();

   useEffect(() => {

This issue body was partially generated by patch-package.

Thanks @avencat
I really think this should be added to the library!


user_func_array() expects parameter 1 to be a valid callback

When trying to run the cheatsheet plug-in on a site using macros I get the following error:
call_user_func_array() expects parameter 1 to be a valid callback, class '__TwigTemplate_3e558ee162291bf865bc4de71ce4454e47ad4d296c107ac8a1735a3102ca9b66' does not have a method 'macro_cs_Position'
Any idea how to get this plug-in to work ?

I'm also receiving the same error on one project and just wanted to document it here. Other projects that use the same Craft and Cheat Sheet versions work great. The more complicated project has a lot of Neo and Matrix fields, but so far I can't figure this out. I'll circle back if I figure out why or a solution.


Possible to start a recording when galicaster is offline

@pmgration said:
"May be desirable so that galicaster starts recording when the software starts but this doesn't seem to happen.."
not completely sure what this means :wink:

From memory, I think it means it's possible to 'start' a recording within peakaboo (just sets recording to true in mongodb), but it doesn't mean that galicaster will be recording (galicaster might not even be running - I don't think there's any checks to ensure it is running for you to start a recording from within peakaboo). In some instances this might be useful, if galicaster started up and saw it was supposed to be recording based on the state in peakaboo, it could start recording immediately.


lldb_function_to_function_dbi: fix a null dereference

C++ allows unnamed arguments.
In the debug info, they are represented as DW_TAG_formal_parameter w/o DW_AT_name.
variable.GetName() here returns NULL for them.
cf. https://github.com/bytecodealliance/wasm-micro-runtime/issues/3187

LGTM


problem with macro 'Bundle'

My code:
"""
use hecs::Bundle;
#[derive(Bundle)]
struct Foo {
x: i32,
y: char,
}
fn main() {
let mut world = World::new();
let e = world.spawn(Foo { x: 42, y: 'a' });
assert_eq!(*world.get::<&i32>(e).unwrap(), 42);
}
"""
I have errors:
error: cannot find derive macro Bundle in this scope
--> src/main.rs:2:10
|
2 | #[derive(Bundle)]
|          ^^^^^^
|
note: Bundle is imported here, but it is only a trait, without a derive macro
--> src/main.rs:1:5
|
1 | use hecs::Bundle;
|     ^^^^^^^^^^^^

You need to enable the macros feature:
https://github.com/Ralith/hecs/blob/122cb6aa682bf4cae7e646109608ac4e97df9b4d/Cargo.toml#L24-L25


Make maximumMessageSize configurable

This moves the code for URLSessionTransport into our library, and makes the maximumMessageSize configurable through the LiveSessionConfiguration.

@carson-katri I think this is the PR you were referring to the other day when we hit the message size limit. But considering we'll be deviating from Phoenix Channels Client in the near(ish) future I assume we can close this?


Removing Apache.NMS dependency.

Removing dependency on Apache.NMS.  This is needed to build Lucene.Net on .NET Core.
-Replaced AtomicReference with use of Interlocked.Exchange.
-Replaced CountDownLatch with CountdownEvent.

Looks great, thanks!
I add a few comments around TestIndexWriterWithThreads, it's not a trivial test and it's worth checking on our CI whether or not it fails before and after your changes. If it fails, it probably fails sporadically.
There is a high risk of introducing thread safety issues here, so I'd want us to cover our bases.
Let's compare the code in this test to the Java version and make sure we are preserving the same behavior. Once we know we do, let's run the tests many times, and strengthen them where possible, to make sure this is air tight.
WDYT?

OK.  Suggested changes have been made.  I also verified that passing tests continue to pass, especially the ones that used to use AtomicReference.

Thanks!


Could not load file or assembly 'T4Toolbox, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'

Hi,
After upgrading to latest version of T4Toolbox i am getting following exception:
Error	1	Errors were generated when initializing the transformation object. The transformation will not be run.  The following Exception was thrown:
System.IO.FileNotFoundException: Could not load file or assembly 'T4Toolbox, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
File name: 'T4Toolbox, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'

Server stack trace:
   at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
   at System.Reflection.RuntimeAssembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
   at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
   at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean forIntrospection)
   at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
   at System.Reflection.Assembly.Load(String assemblyString)
   at System.UnitySerializationHolder.GetRealObject(StreamingContext context)
   at System.Runtime.Serialization.ObjectManager.ResolveObjectReference(ObjectHolder holder)
   at System.Runtime.Serialization.ObjectManager.DoFixups()
   at System.Runtime.Serialization.Formatters.Binary.ObjectReader.Deserialize(HeaderHandler handler, __BinaryParser serParser, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)
   at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize(Stream serializationStream, HeaderHandler handler, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)
   at System.Runtime.Remoting.Channels.CrossAppDomainSerializer.DeserializeObject(MemoryStream stm)
   at System.Runtime.Remoting.Messaging.SmuggledMethodCallMessage.FixupForNewAppDomain()
   at System.Runtime.Remoting.Channels.CrossAppDomainSink.DoDispatch(Byte[] reqStmBuff, SmuggledMethodCallMessage smuggledMcm, SmuggledMethodReturnMessage& smuggledMrm)
   at System.Runtime.Remoting.Channels.CrossAppDomainSink.DoTransitionDispatchCallback(Object[] args)

Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at System.IServiceProvider.GetService(Type serviceType)
   at T4Toolbox.TransformationContext.GetService(Type serviceType)
   at T4Toolbox.TransformationContext..ctor(TextTransformation transformation, StringBuilder generationEnvironment)
   at T4Toolbox.TransformationContext.Initialize(TextTransformation transformation, StringBuilder generationEnvironment)
   at Microsoft.VisualStudio.TextTemplatingBFAB6986108E94B1AC5A0E0C7B4E30903A3BB628F255F90A41F87609AC7BCC13849429B9F13396DC9DB3DC3A521BD2FFADF91307D99A8DB796F7F1B029FDB32F.GeneratedTextTransformation.Initialize() in c:\'mypath'\Model.tt:line 16
   at CallSite.Target(Closure , CallSite , Object )
   at System.Dynamic.UpdateDelegates.UpdateAndExecuteVoid1[T0](CallSite site, T0 arg0)
   at Microsoft.VisualStudio.TextTemplating.TransformationRunner.PerformTransformation()
=== Pre-bind state information ===
LOG: DisplayName = T4Toolbox, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null
 (Fully-specified)
LOG: Appbase = file:///C:/Program Files (x86)/Microsoft Visual Studio 12.0/Common7/IDE/
LOG: Initial PrivatePath = NULL
Calling assembly : (Unknown).
===

I appreciate any help to solve this issue.
Regards,
Assam Zafar

Thanks for reporting this, @Assam. Would you mind collecting more information from your environment?

Run the following command line to collect the codebase information the T4Toolbox package provides to Visual Studio? On my machine, I see entries that point to the T4Toolbox DLLs installed in my user extension cache.

get-childitem -path hkcu:\SOFTWARE\Microsoft\VisualStudio\12.0_Config\RuntimeConfiguration -recurse | where-object {$_.GetValue("name") -like "T4Toolbox*" }

Run fuslogvw, configure it to log all bindings to a custom folder and then repro the problem in Visual Studio. There will be a lot of bindings. You can find those relevant to T4Toolbox by running the following PowerShell command (

get-childitem -path C:\YourFolder -recurse | where-object {$_.name -like "*T4Toolbox*" }

I see both successful and failed binding attempts for T4Toolbox assemblies in my environment.

Build <IP_ADDRESS> has strongly-named assemblies. Can you try it in your environment?
CC: @Assam, @AGeekDad and @Maximushep.

The new version <IP_ADDRESS> works fine.
Thanks for your efforts in resolving this issue and your continuous efforts for this great tool.

Thanks for confirming!


Nitrous.io Quickstart button

Added Nitrous Quickstart files so anyone can quickly spin up a free, cloud dev environment to start using this repo. Clicking the Quickstart button will automatically clone this repo and will install and configure any required packages.

How about adding just a link to an external repository containing the nitrous.json and a short documentation? Maybe like the current "Docker" section. Personally never heard about Nitrous.io and I don't want to maintain it.


Modified parse_file function to include the possibility to read in patterson rcpsp files

Included a function "parse_patterson" to read in RCPSP-instances in Patterson file format.
This file format is (by now) much more wide-spread than the explicit file format of PSPLIB-instances.
The "parse_patterson" method is called, if an RCPSP-instance-file ends with ".rcp".
See also here: https://www.projectmanagement.ugent.be/research/project_scheduling/rcpsp
e.g. datasets RG30 and RG300

Thanks, nice idea :), i had in mind to include some RG instances so this parser will help. should be ok to merge soon.

did you validate that the instances are correct and that let's say a basic solution can be computed with some solver in discrete-optimization ?
on my side i think i would integrate the inclusion of RG30/300 in the datasets.py file and include a test based on 1 given file

Hey! I did compute solutions with the CP-Solver (MiniZinc) which works well, however I have not made any further checks (manually checking resource and precedence feasibility of the generated solution).
Please also note that I had to fix a small bug with my latest commit.
(Was difficult to see because RG30-instances have resource-availabilities of [10, 10, 10, 10] and I mostly tested on RG30 instances. Other instances, such as the sD-data set however may have unequal resource-availabilities such as [16, 12, 13, 15]).

Hi again, yes thanks to have corrected your parser, i looked into it and tested also on sd data and it seems fine.
We added tests and also added some automatic download of RCP datasets in the datasets.py script, in the next PR #197.
do you know if rcp format has been worked also for multimode rcpsp, i don't see it from a first look.
Cheers

Hey! As far as I know, there is no multi-mode .rcp files.
However, there is a set of these "Boctor"-files for the multi-mode case. (See here: https://www.om-db.wi.tum.de/psplib/dataob.html).
However, their file-ending seems to be ".prb". The files are based on this paper: "Heuristics for scheduling projects with resource restrictions and several resource-duration modes", however I did not look deeper into what sort of information is in these files.


Several serious container errors are being reported at the DEBUG level

There are several log messages related to container handling that I think should be promoted from DEBUG level to a higher level, as these represent errors from the user's perspective. This will make it easier for users (like me) to figure out what's going on, as these messages are normally not printed.
Here are a few examples:
12:38:25.785 [container] build -> DEBU 029 Error building Peer container: Error: image bcbrock/golang:latest not found
12:38:25.800 [container] start -> DEBU 031 start-container does not exist, attempting to create API error (404): no such id: dev-vp1-60caf3632e0f43a5a7f14f27115bfaf84f76ee59d3490bbb337703e098ada77fc7b7bddd093f354e8ef89f644330131e5799c966503070b94eb1a83cbc9dc10c
12:38:25.803 [container] start -> DEBU 033 start-could not recreate container no such image
12:57:11.180 [chaincode] LaunchChaincode -> DEBU 09c launchAndWaitForRegister failed Error starting container: no such image

@muralisrini adding a help wanted tag in case someone wants to pick this up. Let me know if you already have a fix.

@bcbrock I've replaced a heap of errors which were being reported at debug in handler.go. The first three that you listed in the OP seems to have been fixed in PR #738.
I've also done a search for debug statements that contain the word fail and adjusted some of them too.


azcopy login --identity failed with ManagedIdentityCredential on 10.24.0

Which version of the AzCopy was used?
10.24.0, Windows AMD64
Note: The version is visible when running AzCopy without any argument
Which platform are you using? (ex: Windows, Mac, Linux)
Windows
What command did you run?
.\azcopy.exe login --identity --identity-client-id "xxx"
Note: Please remove the SAS to avoid exposing your credentials. If you cannot remember the exact command, please retrieve it from the beginning of the log file.
What problem was encountered?

How can we reproduce the problem in the simplest way?
Have you found a mitigation/solution?

I've also tried auto-login but it doesn't work as well:
$env:AZCOPY_AUTO_LOGIN_TYPE="MSI"
$env:AZCOPY_MSI_CLIENT_ID="xxx"
.\azcopy.exe copy --from-to LocalBlob ...
INFO: Scanning...
INFO: azcopy.exe 10.23.0: A newer version 10.24.0 is available to download
Failed to perform Auto-login: ManagedIdentityCredential: ManagedIdentityCredential: Get "http://<IP_ADDRESS>/metadata/identity/oauth2/token?api-version=2018-02-01&client_id=2c955991-c99c-4d84-8284-75fc1c84f075&resource=https%3A%2F%2Fstorage.azure.com": dial tcp <IP_ADDRESS>:80: i/o timeout.

Hi @hyc3z there seems to be a network issue on your system. Is there a firewall or something restricting you from being able to reach the network?

Closing due to inactivity


alipay login  garbled text encoding issues

@wanghaolonggit it relies on your database's encoding, should use utf8mb4.

no, it is a bug.

@hsluoyz  i  fix it , please see the code . https://github.com/casdoor/casdoor/pull/3241


Generate JSON specs on the fly

Issue/Task Number: T430
Overview
This PR enables the OpenAPI json specs to be generated automatically when the YAML specs change.
Changes

Add EWallet.Web.APIDocs.JSONGenerator
Add the generator to AdminAPI.Application and EWalletAPI.Application so the yaml specs are monitored

Implementation Details

This feature adds a new dependency: :file_system, which is also used by :phoenix_live_reload
The generator is implemented as a GenServer so that it does not block the ewallet server

Usage
Run mix omg.server and try touch or update the spec.yaml files. The server should output the following:
$ mix omg.server
[info] Setting up websockets dispatchers...
[info] Running UrlDispatcher.Plug with Cowboy http on port 4000
[info] Changes detected at /vagrant/apps/ewallet_api/priv/spec.yaml. Regenerating JSON API specs...
[info] JSON OpenAPI spec generated successfully at /vagrant/apps/ewallet_api/priv/spec.json

Impact
No DB changes. No API changes.

Not sure if I like the idea of adding Java as runtime dependencies (= we will need it everywhere), especially when the spec is pretty much static? 🤔 I think having a pre-commit hook and force anyone who modifies the YAML spec to generate JSON spec (and commit that) might be a better approach.

Imho, I don't trust (myself with) pre-commit hooks as it relies on the committer setting up the hook and not skip it. Personally it would be nice if we could at least generate it during the build and not runtime?
Or maybe it's time to look for alternative to OpenAPI together given the limitations we're discovering... 🤔


Import projects

Does anyone know the folder location of projects being worked on?
I'm asking as I would like to import an existing project and continue building with AutoDev.

#31 this is being worked on, the project is not on your local filesystem.


SecurityConfiguration create in offline will not take short name

The offline create(name, type, provider) usually will take a shortened version of the class name for type. The aliases are set up to only allow a short type.  OracleUnifiedDirectoryAuthenticator and VirtualUserAuthenticator that will not take a shortened name in offline. create and deploy are broken if the alias definition is NOT set to long name for offline wlst_type. However, a lookup of the wlst_type when the alias definition IS set to the long name fails.
Need to come up with an appropriate strategy.
FYI, create always succeeds in both online and offline with the full class name.

Converted to Jira WDT-282


Compatibility of Amplify CD with npm 9

Before opening, please confirm:

[X] I have checked to see if my question is addressed in the FAQ.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

App Id
d2d6ty1wlg8jch
AWS Region
us-east-1
Amplify Hosting feature
Build settings, Deployments, Frontend builds
Frontend framework
Angular
Next.js version
N/A
Next.js router
N/A
Describe the bug
Amplify CD fails when trying to patch Amplify CLI to 12.0.3. This started after our build image upgraded the version of npm being used to 9
Expected behavior
The build runs to completion without failing
Reproduction steps

Create a custom build image. The image must use npm version 9
Upload image to an Elastic Container Registry. Copy URI of image
In AWS Amplify -> Build settings. In Build image settings set Custom image to URI from previous step
Deploy app.

Build Settings
version: [VERSION-NUMBER]
backend:
  phases:
    preBuild:
      commands:
        - ./amplify-deploy-backend.sh
    build:
      commands:
        - amplifyPush --simple

frontend:
  phases:
    build:
      commands:
        - frontend/amplify-deploy-frontend.sh
  artifacts:
    baseDirectory: frontend/dist/amplify
    files:
      - '**/*'
  cache:
    paths:
      - 'frontend/node_modules/**/*'
      - 'node_modules/**/*'

Log output

# Put your logs below this line
2023-06-22T15:45:42.639Z [INFO]: Git SSH Key acquired
2023-06-22T15:45:42.742Z [INFO]: # Cloning repository: git@gitlab.com:user/repo.git
2023-06-22T15:45:46.656Z [INFO]: Agent pid 157
2023-06-22T15:45:46.740Z [INFO]: Identity added: /root/.ssh/git_rsa (/root/.ssh/git_rsa)
                                 Cloning into 'repo'...
                                 Warning: Permanently added the ECDSA host key for IP address '<IP_ADDRESS>' to the list of known hosts.
2023-06-22T15:45:46.741Z [INFO]: # Switching to commit: [COMMIT-HASH]
2023-06-22T15:45:46.894Z [INFO]: Agent pid 170
2023-06-22T15:45:46.895Z [INFO]: Identity added: /root/.ssh/git_rsa (/root/.ssh/git_rsa)
                                 Note: switching to '[COMMIT-HASH]'.
                                 You are in 'detached HEAD' state. You can look around, make experimental
                                 changes and commit them, and you can discard any commits you make in this
                                 state without impacting any branches by switching back to a branch.
                                 If you want to create a new branch to retain commits you create, you may
                                 do so (now or later) by using -c with the switch command. Example:
                                 git switch -c <new-branch-name>
                                 Or undo this operation with:
                                 git switch -
                                 Turn off this advice by setting config variable advice.detachedHead to false
                                 HEAD is now at [SHORT-COMMIT-HASH] remove spaces added to trigger backend-name graphql/pt lambda push
2023-06-22T15:45:46.905Z [INFO]: Successfully cleaned up Git credentials
2023-06-22T15:45:46.906Z [INFO]: # Checking for Git submodules at: /codebuild/output/src654124366/src/repo/.gitmodules
2023-06-22T15:45:46.912Z [INFO]: # Retrieving environment cache...
2023-06-22T15:45:46.965Z [INFO]: # Retrieved environment cache
2023-06-22T15:45:46.965Z [INFO]: ---- Setting Up SSM Secrets ----
2023-06-22T15:45:46.965Z [INFO]: SSM params {"Path":"/amplify/hash/backend-name/","WithDecryption":true}
2023-06-22T15:45:47.024Z [INFO]: # Determining if there are buildable backend changes in the amplify directory of the repository...
2023-06-22T15:45:47.037Z [INFO]: # Last built commit: [COMMIT-HASH]
2023-06-22T15:45:47.046Z [INFO]: # No differences detected.
2023-06-22T15:45:47.055Z [WARNING]: Command failed: source ~/.bashrc 2> /dev/null || true && nvm current
2023-06-22T15:45:47.056Z [INFO]: # Patching NPM package '@aws-amplify/cli' to 12.0.3...
2023-06-22T15:45:47.317Z [INFO]: npm
2023-06-22T15:45:47.318Z [INFO]: ERR! `user` is not a valid npm option
2023-06-22T15:45:47.319Z [INFO]:
2023-06-22T15:45:47.320Z [INFO]: npm ERR!  Error patching NPM package '@aws-amplify/cli' to version 12.0.3. Verify the package name and version are correct, and retry the build. For help see our docs: https://docs.aws.amazon.com/amplify/latest/userguide/custom-build-image.html
2023-06-22T15:45:47.323Z [WARNING]: ! Unable to patch packages...
2023-06-22T15:45:47.323Z [INFO]: # Starting environment caching...
2023-06-22T15:45:47.323Z [INFO]: # Uploading environment cache artifact...
2023-06-22T15:45:47.425Z [INFO]: # Uploaded environment cache artifact
2023-06-22T15:45:47.425Z [INFO]: # Environment caching completed

Additional information
I suspect it has something to do with this

Hi @mohammedsahl 👋 , thanks for reaching out. I observed that the latest builds on your Amplify app d2d6ty1wlg8jch have completed successfully. Also, I wasn't able to reproduce the outlined behavior when using a custom build image with npm v9. By default, the Amazon Linux:2023 build image has npm v9 and Amplify CLI v12.8.2 installed. Now, if you add a live package override to set the Amplify CLI package to the latest version, the patching does complete successfully at build time:
# Patching NPM package ‘@aws-amplify/cli’ from 12.8.2 to 12.10.1...
2024-02-14T19:35:38.559Z [INFO]: # Installed ‘<EMAIL_ADDRESS>2024-02-14T19:35:38.711Z [INFO]: # Done patching NPM package ‘@aws-amplify/cli’ to version 12.10.1

I see that your app is using a custom image hosted on Amazon ECR and the root cause seems related to the npm configuration on the custom image. Its very likely that this breaking change introduced with npm v9 led to the patching to fail.
I am going to close this thread since the latest builds have succeeded.


Current ballerina methods doesn't support implicit parameter casting

The current ballerina implementation doesn't support implicit casting for parameters, that is if there is a function signature as [1], we cannot invoke that function with an integer parameter, this happens because the function stored in symbolMap with a key which includes parameter types as well. So for example, function [1] is defined in symbol map with key "abc.float" so it is not visible when searched for a function which can accept integer (abc.int) parameter.
With current implementation, you can't define a variable name same as a function name if that function has no parameters because in that case symbolMap key will be same for both
[1] - function abc(float b)

BTW we don't have long any more .. just int and float. But your issue applies for that case too.

fixed with pull - https://github.com/ballerinalang/ballerina/pull/2173

pull request merged, hence resolving


Scaffold main crate with common traits and features.

I've decided to switch to a single repository design because the backends will have to depend on the main crate for function implementations (which will depend on that backend), creating a dependency loop.

Well, that cyclic dependency could simply be resolved by having an additional crate that holds these.
On the other hand, I think we shouldn't think too big in the very beginning. we can keep refactoring as we go, so I'm also all for a simple design (mostly single crate).


Hyundai: explicitly copy signals to forward (#28020)

Reverts commaai/openpilot#28406
let's see if tests catch!

It did fail for some Hyundai by generating these carControl msg:
https://github.com/commaai/openpilot/actions/runs/5319882482/jobs/9632915697?pr=28604#step:5:10073


partially revert 29b35a33 to fix typo

Yes, I probably do want to submit a typo fix to the main repo :-)

FYI, This was fixed in #919 and merged to dev branch.


[d3d8] Railroad Tycoon 3 - zoomed in terrain shuffle

This is going to be a rather hard one to describe, so I've captured a video. The TLDR of it is that when scrolling through some of the closest zoom levels on the game map, the terrain textures sort of shuffle around in a crazy dance.
I've captured a trace, but since the game does "wonderful" things with buffers, apitrace has mostly caught garbage. The issue can be seen in the trace as well though, among the madness.
Software information
Railroad Tycoon 3
System information

GPU: RTX 4070
Driver: 535.183.01
Wine version: 9.12 Staging
DXVK version: fe9c875

Apitrace file(s)
RT3.trace.tar.xz
Log files
RT3.log

Could be an ANV bug, but on Intel the game doesn't render geometry properly at all and ultimately fails with:
/usr/i686-w64-mingw32/include/c++/13.1.0/array:202: constexpr std::array<_Tp, _Nm>::value_type& std::array<_Tp, _Nm>::operator[](size_type) [with _Tp = dxvk::DxsoSemantic; unsigned int _Nm = 32; reference = dxvk::DxsoSemantic&; size_type = unsigned int]: Assertion '__n < this->size()' failed.

New set of logs, collected with a debug build from @K0bin: RT3.log

We just fixed the Intel crash at least.

Apparently it crashes on ANV inside vkCreateGraphicsPipeline now.

RT3 validation errors.txt


Fetching parent keys returns "Undefined index"

Let's say, I have such setting in a config:
/* myconfig.php */
return [
   'triggers' => [
      'ctr' => 15,
      'cpc' => 16
   ]
];

In an app, I fetch these values using your package:
$triggers = Setting::get('myconfig.triggers');

Works fine, as it gets values from Config. Then, let's say, we want to change one (only one) value of it:
Setting::set('myconfig.triggers.ctr', 20);

Now, when I call same "get", I get an exception:
ErrorException (E_UNKNOWN)
Undefined index: myconfig.triggers
/vendor/cornford/setter/src/Cornford/Setter/SettingBase.php:142
Code: if ($results[$key] === '""') {

... and not sure how to fix it. I believe here you've just got a value from database with index "myconfig.triggers.ctr" - so probably can just grab and use it instead? Like:
$key = reset( array_keys($results) );

Happy New Year!
Didn't make thorough tests on this, but from initial perspective it looks like it works correctly. Thanks!

Happy new year!
No worries. Hope you find this package useful =)


added punctuations

Before submitting a pull request, please make sure the following is done...

Fork the repo and create your branch from master.
If you've added code that should be tested, add tests!
If you've changed APIs, update the documentation.
Ensure that:

The test suite passes (npm test)
Your code lints (npm run lint) and passes Flow (npm run flow)
You have followed the testing guidelines

If you haven't already, complete the CLA.

Please use the simple form below as a guideline for describing your pull request.
Thanks for contributing to Draft.js!

Summary
[...]
Test Plan
[...]

Doing some triaging/cleanup so I'll close this for now due to inactivity. Feel free to comment on this to re-open it if you do get back on it (:


Deployment branches missing/hidden since new Amplify UI

Before opening, please confirm:

[X] I have checked to see if my question is addressed in the FAQ.
[X] I have searched for duplicate or closed issues.
[X] I have removed any sensitive information from my code snippets and submission.

Amplify Hosting feature
Frontend builds, One click deploy
Is your feature request related to a problem? Please describe:
Hi all!
Since the new Amplify UI in the AWS Console some of my deployment branches in an Amplify app (dpzme52p5orzv) are missing (or hidden in the Amplify UI). I know they are still there because deployments still work, they're listed in some other places (like when adding a branch, or showing the custom domains mapped to branches).
I've checked some other Amplify apps, and it sees the branches of other apps are shown.
Describe how you'd like this feature to work
Show all branches

Hello -- sorry for the frustration here. I've marked this as a bug and the team is working on a fix ASAP


Key Vault Access Policy GUI has been changed

Module: 3
Lab/Demo: 10
Task: Multiple
Step: Multiple
Description of issue
The Key Vault access policy GUI has changed substantially in the Portal
the lab steps do not match the new portal updates
Repro steps:
You will need to run through the labs as my students were saying that there were several locations where the lab instructions differ from the new portal changes.

Please share a detailed list of the anomalies experiended.
Thanks.

Azure has just changed the way that you submit a change to the Azure Key
Vault access policy. It is completely different than before (with good
reason) the previous method was crazy as you could see the change made but
if you did not click save the change was not made.Now you make the change
and its saved automatically.
Therefore the access policy section of the lab needs to be updated..
Thanks.
On Thu, 3 Nov 2022 at 09:14, serling1962 @.***> wrote:

Please share a detailed list of the anomalies experiended.
Thanks.
—
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftLearning/AZ500-AzureSecurityTechnologies/issues/289#issuecomment-1301480333,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEO5IEXLX6VIM4IYNNF7AV3WGLYVHANCNFSM6AAAAAARUVWPNA
.
You are receiving this because you authored the thread.Message ID:
<MicrosoftLearning/AZ500-AzureSecurityTechnologies/issues/289/1301480333@
github.com>

Updated Azure Key Vault fields.


[doc] Issue in "Build the installation media"

Build the installation media:
https://documentation.suse.com/suse-edge/3.0/single-html/edge/#build-installation-media
Missing the unattended section.

Closed by https://github.com/suse-edge/suse-edge.github.io/pull/406


Added permissions needed to remove rbac user db from s3

This change adds permissions to the administrative policy to let the uninstaller remove the S3 bucket policy and then delete some objects

These changes were included in https://github.com/fugue/fugue-user-iam-templates/pull/3.
This can be closed.


[refactor][extract] fix crash

We didn't find the begin/end statements in the CS sometimes when selecting ObjC properties because of PseudoObjectExpr

Right, it would be good to merge everything into one search pass! I'll update.


Adding builder pattern for encryption client initialization and removing Beta interface

This PR include -

Added CosmosEncryptionClientBuilder for creating CosmosEncryptionAsyncClient and CosmosEncryptionClient , in line with Track2 libs including cosmos core lib.
Deleted Beta interface from encryption lib , and removed deleteAllItemsByPartitionKey() and queryChangeFeed() from public surface area, will add them back once it is GAed in cosmos core lib.

API changes have been detected in com.azure:azure-cosmos-encryption. You can review API changes here


Make the style of the app better

Description
I think the game style is pretty basic, maybe find solution to make it better ( colors, general design ... )

Ideas

change font of the app ( use Roboto or smthing else) see: https://fonts.google.com/
Change bg color and line style


tlgen.py cannot found the keyword 'clock'

The command i run is 'tlgen -t ../data/xbar_main.hjson -o ~/work/opentitan/hw/top_englishbreakfast/ip --ip-path ./xbar_main/'.
Then, tlgen report below:
Traceback (most recent call last):
  File "/home/guozhiyang/work/opentitan/util/tlgen.py", line 94, in <module>
    main()
  File "/home/guozhiyang/work/opentitan/util/tlgen.py", line 71, in main
    xbar = tlgen.validate(obj)
  File "/home/guozhiyang/work/opentitan/util/tlgen/validate.py", line 253, in validate
    xbar.clock = obj["clock"].lower()
KeyError: 'clock'

I check validate.py and xbar_main.hjson, and I did not find the keyword 'clock' in addition to the keyword 'nodes' , should i change line 253 of validate.py to 'xbar.clock = obj['nodes'][n]['clock'].lower()' or 'xbar.clock = obj["clock_primary"].lower()'?
When i change line 253 to 'xbar.clock = obj["clock_primary"].lower()' and line 254 to 'xbar.reset = obj["reset_primary"].lower()', it reports below:
ERROR: main missing required key clock
ERROR: main missing required key reset
ERROR: main missing required key clock_connections
WARNING: main contains extra key clock_primary
WARNING: main contains extra key other_clock_list
WARNING: main contains extra key reset_primary
WARNING: main contains extra key other_reset_list
ERROR: main nodes missing required key stub
ERROR: main nodes missing required key stub
ERROR: main nodes missing required key stub
ERROR: main nodes missing required key stub
ERROR: main nodes missing required key stub
ERROR: main nodes missing required key stub
ERROR: main nodes missing required key stub
ERROR: main nodes missing required key stub
ERROR: main nodes missing required key stub
ERROR: main nodes missing required key stub
ERROR: main nodes missing required key stub
ERROR: main nodes missing required key stub
ERROR: main nodes missing required key stub
ERROR: main nodes missing required key stub
ERROR: main nodes missing required key stub
ERROR: main nodes missing required key stub
ERROR: main has top level error. Aborting
ERROR: Hjson structure error
Traceback (most recent call last):
  File "/home/guozhiyang/work/opentitan/util/tlgen.py", line 94, in <module>
    main()
  File "/home/guozhiyang/work/opentitan/util/tlgen.py", line 72, in main
    xbar.ip_path = args.ip_path
AttributeError: 'NoneType' object has no attribute 'ip_path'

hmmm.. .there's a chance some of the gen stuff here is a bit out dated.
A lot of our tlgen functionality has been folded into topgen.
@eunchan would know the best.

Thanks a lot!
But, when I run topgen, it needs the absolute path of topcfg, otherwise it will give the following error:
Traceback (most recent call last):
  File "/home/guozhiyang/work/opentitan/util/topgen.py", line 1322, in <module>
    main()
  File "/home/guozhiyang/work/opentitan/util/topgen.py", line 1078, in main
    cfg_path = Path(args.topcfg).parents[1]
  File "/usr/lib/python3.8/pathlib.py", line 621, in __getitem__
    raise IndexError(idx)
IndexError: 1

In addition, running the following command will not find the keyword "module"：
topgen -t /home/guozhiyang/work/opentitan/hw/top_englishbreakfast/data/xbar_main.hjson -o ~/work/opentitan/hw/top_englishbreakfast/ip -v --xbar-only
reports:
DEBUG: Generation pass 0
Traceback (most recent call last):
  File "/home/guozhiyang/work/opentitan/util/topgen.py", line 1322, in <module>
    main()
  File "/home/guozhiyang/work/opentitan/util/topgen.py", line 1129, in main
    _process_top(cfg_copy, args, cfg_path, out_path_gen, pass_idx)
  File "/home/guozhiyang/work/opentitan/util/topgen.py", line 744, in _process_top
    templated_list = lib.get_templated_modules(topcfg)
  File "/home/guozhiyang/work/opentitan/util/topgen/lib.py", line 336, in get_templated_modules
    print(top['module'])
KeyError: 'module'


Script to add lila, MATH, gsm8k, naturalproofs-gen

Description

Related Issue

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Chore (non-breaking change that does not add functionality or fix an issue)

Checklist:

[ ] I have read the Code of Conduct
[ ] I have updated the documentation accordingly.
[ ] All commits are GPG signed

Hello @2lambda123! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file proof-pile-v2/math_datasets/process_math_datasets.py:

Line 25:80: E501 line too long (100 > 79 characters)
Line 39:80: E501 line too long (100 > 79 characters)
Line 83:5: E122 continuation line missing indentation or outdented
Line 84:5: E122 continuation line missing indentation or outdented
Line 85:5: E122 continuation line missing indentation or outdented
Line 86:1: E122 continuation line missing indentation or outdented
Line 187:5: E122 continuation line missing indentation or outdented
Line 188:5: E122 continuation line missing indentation or outdented
Line 189:1: E122 continuation line missing indentation or outdented
Line 214:80: E501 line too long (80 > 79 characters)
Line 256:5: E122 continuation line missing indentation or outdented
Line 257:5: E122 continuation line missing indentation or outdented
Line 258:5: E122 continuation line missing indentation or outdented
Line 259:1: E122 continuation line missing indentation or outdented
Line 283:80: E501 line too long (80 > 79 characters)
Line 335:80: E501 line too long (94 > 79 characters)
Line 336:80: E501 line too long (84 > 79 characters)
Line 382:80: E501 line too long (80 > 79 characters)


Modify subprocess error/info

On a machine without tcsh installed run_subprocess(['mne', 'make_scalp_surfaces', '--subject', subject]) returns following:

Command not found: mkheadsurf
...
subprocess.CalledProcessError: Command '['mne', 'make_scalp_surfaces', '--overwrite', '--subject', 'sample', '--force']' returned non-zero exit status 1.
('', '')

Would a PR to make error message more meaningful be useful?

I don't think it's related to tcsh. Is freesurfer sourced properly in
the tcsh shell?

I believe so. Have always sourced it as source $FREESURFER_HOME/SetUpFreeSurfer.sh. But now we can't reproduce it on the said machine after removing tcsh.  Must have been a ghost between keyboard and chair 😕 Sorry for the inconvenience. Closing this down.

@agramfort FWIW I uninstalled tcsh and encountered this TB again, and resolved once tcsh was reinstalled. Not sure what this can be?

Traceback (most recent call last):
File "/home/nordme/GitHub/mne-python/mne/commands/mne_make_scalp_surfaces.py", line 133, in
run()
File "/home/nordme/GitHub/mne-python/mne/commands/mne_make_scalp_surfaces.py", line 60, in run
options.no_decimate, options.verbose)
File "", line 2, in _run
File "/home/nordme/GitHub/mne-python/mne/utils.py", line 797, in verbose
return function(*args, **kwargs)
File "/home/nordme/GitHub/mne-python/mne/commands/mne_make_scalp_surfaces.py", line 94, in _run
Command not found: mkheadsurf
env=this_env)
File "", line 2, in run_subprocess
File "/home/nordme/GitHub/mne-python/mne/utils.py", line 797, in verbose
return function(*args, **kwargs)
File "/home/nordme/GitHub/mne-python/mne/utils.py", line 1304, in run_subprocess
p = subprocess.Popen(command, *args, **kwargs)
File "/home/nordme/miniconda3/envs/mne/lib/python3.6/subprocess.py", line 709, in init
restore_signals, start_new_session)
File "/home/nordme/miniconda3/envs/mne/lib/python3.6/subprocess.py", line 1344, in _execute_child
raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: 'mkheadsurf': 'mkheadsurf'
Traceback (most recent call last):
File "/home/nordme/GitHub/Scripts/run_fs_recon_mne_bem.py", line 142, in
'--overwrite', '--subject', subject, '--force'])
File "", line 2, in run_subprocess
File "/home/nordme/GitHub/mne-python/mne/utils.py", line 797, in verbose
return function(*args, **kwargs)
File "/home/nordme/GitHub/mne-python/mne/utils.py", line 1321, in run_subprocess
raise subprocess.CalledProcessError(p.returncode, command, output)
subprocess.CalledProcessError: Command '['mne', 'make_scalp_surfaces', '--overwrite', '--subject', 'genz102_9a', '--force']' returned non-zero exit status 1.
('', '')
Process finished with exit code 1

if you call mne shell scripts or freesurfer they were written for tcsh


How to set fields to null literral in go

Description of the bug:

I'm using cdk8s with go and I'm having trouble setting some fields to null literal.
Why do I need to set fields to null in the first place?
When creating/updating resource using kubectl apply, it does a 3 way merge between the existing k8s resource on the cluster and what you want to apply.
For instance, if you already have a k8s resource with a foo: bar label like:
apiVersion: v1
kind: ConfigMap
metadata:
  labels:
    foo: bar
    baz: baz
  name: my-cm

and you want to remove the foo label, applying a resource like:
apiVersion: v1
kind: ConfigMap
metadata:
  labels:
  # no more foo label
    baz: baz
  name: my-cm

is not enough because of the 3 way merge. It will work if you try to apply the same manifest to a brand new k8s cluster but not on one where the my-cm configmap already have the foo label.
A common trick I've used in the past and that was implemented in https://github.com/kubernetes/kubernetes/pull/40630 is to set the field you want to remove to null literal:
apiVersion: v1
kind: ConfigMap
metadata:
  labels:
    foo: null
    baz: baz
  name: my-cm

This yaml manifest will remove the foo label if it's already present in the existing resource.
Reproduction Steps:

This is my test cdk8s app:
package main

import (
	"fmt"

	"example.com/cdk8s-demo/imports/k8s"
	"github.com/aws/jsii-runtime-go"
	"github.com/cdk8s-team/cdk8s-core-go/cdk8s/v2"
)

func main() {
	app := cdk8s.NewApp(&cdk8s.AppProps{})

	chart := cdk8s.NewChart(app, jsii.String("my-chart"), &cdk8s.ChartProps{})

	labels := map[string]*string{
		"foo": jsii.String("bar"),
		"set-to-null": jsii.String("to-be-replaced"),
	}
	k8s.NewKubeConfigMap(chart, jsii.String("my-cm"), &k8s.KubeConfigMapProps{
		Metadata: &k8s.ObjectMeta{
			Labels: &labels,
		}})
	fmt.Println(*app.SynthYaml())
}

It a go module named example.com/cdk8s-demo/imports/k8s.
Under example.com/cdk8s-demo/imports/k8s I've imported k8s api objects using cdk8s import k8s -l go.
When run using go run main.go it produce:
apiVersion: v1
kind: ConfigMap
metadata:
  labels:
    foo: bar
    set-to-null: to-be-replaced
  name: my-chart-my-cm-c841940f

Environment:

Framework Version: github.com/cdk8s-team/cdk8s-core-go/cdk8s/v2 v2.68.71
OS: linux

Other:
What I have already tried:
Using "set-to-null": jsii.String(""), -> it renders an empty string in the yaml (expected).
Using "set-to-null": jsii.String("null"), -> it renders a "null" string in the yaml (expected).
Using json-patch:
package main

import (
	"fmt"

	"example.com/cdk8s-demo/imports/k8s"
	"github.com/aws/jsii-runtime-go"
	"github.com/cdk8s-team/cdk8s-core-go/cdk8s/v2"
)

func main() {
	app := cdk8s.NewApp(&cdk8s.AppProps{})

	chart := cdk8s.NewChart(app, jsii.String("my-chart"), &cdk8s.ChartProps{})

	labels := map[string]*string{
		"foo": jsii.String("bar"),
		"set-to-null": jsii.String(""),
	}
	cm:=k8s.NewKubeConfigMap(chart, jsii.String("my-cm"), &k8s.KubeConfigMapProps{
		Metadata: &k8s.ObjectMeta{
			Labels: &labels,
		}})

	cm.AddJsonPatch(cdk8s.JsonPatch_Replace(jsii.String("/metadata/labels/set-to-null"),"null"))
	fmt.Println(*app.SynthYaml())
}

cm.AddJsonPatch(cdk8s.JsonPatch_Replace(jsii.String("/metadata/labels/set-to-null"),"null")) -> render a "null" string in yaml
cm.AddJsonPatch(cdk8s.JsonPatch_Replace(jsii.String("/metadata/labels/set-to-null"),"")) -> render a "" string in yaml
Using pointer to empty interface:
	var i interface{}
	cm.AddJsonPatch(cdk8s.JsonPatch_Replace(jsii.String("/metadata/labels/set-to-null"), &i))

-> it removes the field completely.
I think a json path like {"op": "replace","path": "/metadata/labels/set-to-null","value": null} should work but I think the null literal in the json patch is lost at some point when go ---call---> jsii ---call---> typescript.

This is :bug: Bug Report

Nice one. I think JsonPatch is an ok API for this, assuming it works of course :)
The thing is, it does work in typescript:
cdk8s.ApiObject.of(cm).addJsonPatch(cdk8s.JsonPatch.replace('/metadata/labels/set-to-null', null));

In golang, the offending code the auto generated validations jsii produces:

I've tried to make my own version of JsonPatch_Replace in order to bypass the validation that prevent me from passing nil as the value of the patch:
package main

import (
	"fmt"

	"example.com/cdk8s-demo/imports/k8s"
	"github.com/aws/jsii-runtime-go"
	"github.com/cdk8s-team/cdk8s-core-go/cdk8s/v2"

	_jsii_ "github.com/aws/jsii-runtime-go/runtime"
	_init_ "github.com/cdk8s-team/cdk8s-core-go/cdk8s/v2/jsii"
)

func main() {
	app := cdk8s.NewApp(&cdk8s.AppProps{})

	chart := cdk8s.NewChart(app, jsii.String("my-chart"), &cdk8s.ChartProps{})

	labels := map[string]*string{
		"foo":         jsii.String("bar"),
		"set-to-null": jsii.String(""),
	}
	cm := k8s.NewKubeConfigMap(chart, jsii.String("my-cm"), &k8s.KubeConfigMapProps{
		Metadata: &k8s.ObjectMeta{
			Labels: &labels,
		}})

	var i interface{}
	// cm.AddJsonPatch(cdk8s.JsonPatch_Replace(jsii.String("/metadata/labels/set-to-null"), &i))
	cm.AddJsonPatch(no_validation_JsonPatch_Replace(jsii.String("/metadata/labels/set-to-null"), &i))
	fmt.Println(*app.SynthYaml())
}

func no_validation_JsonPatch_Replace(path *string, value interface{}) cdk8s.JsonPatch {
	_init_.Initialize()

	var returns cdk8s.JsonPatch

	_jsii_.StaticInvoke(
		"cdk8s.JsonPatch",
		"replace",
		[]interface{}{path, value},
		&returns,
	)

	return returns
}

It doesn't break while going through jsii but it produces:
apiVersion: v1
kind: ConfigMap
metadata:
  labels:
    foo: bar
  name: my-chart-my-cm-c841940f

@tgermain I've opened a jsii issue. not much we can do on cdk8s side.


fix dumping of active failover agency

Scope & Purpose
at the end of the test we should dump the agency - just in case. This fixes the authentification to fix dumping.

[x] :hankey: Bugfix

only unrelated issues.


Allow to enable alias for OpenAPI310PydanticSchema

I use a pydantic model to serialize some data and return as a response. Some fields have alias.
The problem is that OpenAPI310PydanticSchema always returns property names taken from alias, while default is False. So there's a mismatch between the actual output and OpenAPI310PydanticSchema when by_alias is False (default)

examples please

from pydantic import BaseModel, Field
from pydantic_openapi_schema.utils.utils import (
    OpenAPI310PydanticSchema,
    construct_open_api_with_schema_class,
)
from pydantic_openapi_schema.v3_1_0 import OpenAPI

class User(BaseModel):
    id: int
    name: str = Field(alias="Another")

User(id=0, Another="name").dict()
parameters = [
    {
        "name": "id",
        "in": "path",
        "description": "ID of the document",
        "required": True,
        "style": "simple",
        "explode": False,
        "schema": {"type": "integer", "format": "int64"},
    }
]
get_object = dict(
    # parameters=parameters,
    responses={
        "200": dict(
            description="response.",
            content={"application/json": dict(schema=OpenAPI310PydanticSchema(schema_class=User))},
        )
    },
)
info = dict(
    title="API",
    version="1.0",
    description=""
)
base_schema = dict(
    info=info,
    paths={},
        paths={"/document/{document_id}": {"get": get_object}}

)

construct_open_api_with_schema_class(OpenAPI.parse_obj(base_schema))
construct_open_api_with_schema_class(OpenAPI.parse_obj(base_schema)).dict(by_alias=False, exclude_none=True)

It returns Another as property name, while should be name

I see. So it doesn't propagate the alias true.
Want to add a PR?

It does not propagate alias true or false for passed OpenAPI310PydanticSchema.
construct_open_api_with_schema_class returns OpenAPI which has its own aliases like $ref > ref which shouldn't be touched.
If you point me to where do you think it should be changed, I can do it
If you point me

well, you can add optional kwargs to construct_open_api_with_schema_class and propagate these to the OpenAPI310PydanticSchema class. Or you can update the OpenAPI310PydanticSchema with a config that favors aliases.


greenmask restore fails for generated columns

I'm running greenmask reset --config config.yml latest and it fails when trying to restore a table with a generated column. I'm testing without applying transformations to any of the columns of the table that contains the generated column I get the following error message:
FTL fatal error="data stage restoration error: at least one worker exited with error: unable to perform restoration task (worker 4 restoring table \"public\".\"asdfasdf\"): error from postgres connection msg = column \"state\" is a generated column code=42P10"
According to the postgres documentation A generated column cannot be written to directly. In INSERT or UPDATE commands, a value cannot be specified for a generated column, but the keyword DEFAULT may be specified., so I have also tried to apply the following transformation:
dump:
  transformation:
    - schema: 'public'
      name: 'asdfasdf'
      transformers:
        - name: 'Replace'
          params:
            column: 'state'
            value: DEFAULT

but I get the same error message. I only get the restore to work if I ignore the table that has a column generated when doing the dump. I don't know if this is a bug or if greenmask simply doesn't support this type of columns. I hope you will give me the answer.
My specs:

Greenmask 0.1.10
PostgreSQL 14.11

Hi @MamesPalmero! Thank you for reporting. I will explore your issues and get back soon

I've checked your case. So I need to exclude generated columns from COPY statement. I will fix it as soon as possible.

Fixed. You can build the main branch manually by calling make build or wait for the next release (expected the next week)

Published in v0.1.11


Revert "New version: TortoiseHg.TortoiseHg version 6.9rc0 (#194814)"

This reverts commit 4139c17bf6bce3f48782d48ea2d2a3891a195162.
Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
[ ] ~Is there a linked Issue?~

Manifests

[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

Microsoft Reviewers: Open in CodeFlow

This reverts the change from #194814 because this introduces a pre-release version into the release manifest.
If pre-release versions are desired, create a separate manifest. There are plenty of examples with RC, Beta etc. within the repo.

@SpecterShell could you check your automation so that it skips RC versions?

@SpecterShell could you check your automation so that it skips RC versions?

Just fixed it: https://github.com/microsoft/winget-pkgs/pull/194814#issuecomment-2507872869


Tidy up channel presets

Some inconsistencies in channel preset lists I noticed during the development of Open Fixture Library's QLC+ 4.12.0 plugin (see OpenLightingProject/open-fixture-library#547).
Also, there is the PositionPanCounterClockwise channel preset, but no matching clockwise or Tilt presets. Is this a mistake?
When adding / removing / renaming a preset, one always needs to do so in various different places:

XSD schema
fixture tool
qlcchannel.h
qlcchannel.cpp 2 times
qlccapability.h
qlccapability.cpp
maybe more "fixed" places
and of course everywhere it is used, i.e. fixtures and code like strobe frequency preview

Would it be a good idea to add some kind of a checklist somewhere to reduce the risk of missing something? (We have this for OFL, too; see https://github.com/OpenLightingProject/open-fixture-library/blob/master/docs/capability-types.md#how-to-add-new-capability-types--type-specific-properties)

PositionPanCounterClockwise made sense when I first added it.
Then I worked on Monitor properties and now there is a flag to invert pan/tilt there. It was Jano's suggestion to cope with channels inverted from the product menu.
Now PositionPanCounterClockwise can be removed and eventually users will invert from channel properties. The important thing is that there is a way to tell previews how to handle pan/tilt channels.
As for checklist, I agree, but at the moment I have zero time. I am going to release 5.0.0 Alpha3 today.
The proper place could be GitHub Wiki.

I also did the checklist (and a bit of documentation), but I don't have write access to the QLC+ GitHub Wiki, so I created a gist: https://gist.github.com/FloEdelmann/1ad10d637fc932e633f989f4c50835bf. Feel free to modify it and copy it to the Wiki, I will then delete my gist again.
I'd add a link to the Wiki page (as soon as it exists) as code comments in all the places listed above, so please don't immediately merge this PR.

@FloEdelmann Thanks a lot!
I've added the page to the wiki and linked in the main page (developers corner)

Okay, I've added the comments, so now I think this PR is finished :)

Thanks @FloEdelmann ! :+1: