add services and toc

Updating for

monitor-query
attestation

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

File
Status
Preview URL
Details

docs-ref-mapping/reference-unified.yml
:white_check_mark:Succeeded

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

#fixes https://github.com/Azure/azure-sdk-for-js/issues/18308

@danieljurek Can you please review?

Please move this under the "Monitor" service. That's consistent with how we handled Identity:

The hierarchy should be "Monitor" > "Client" > "Monitor Query".

@danieljurek what is the azure-monitor under monitor service in the TOC? i see it in TOC but not on docs - https://docs.microsoft.com/en-us/javascript/api/overview/azure/monitor?view=azure-node-latest

Docs Build status updates of commit 5a61e27:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-mapping/reference-unified.yml
:white_check_mark:Succeeded

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

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

File
Status
Preview URL
Details

preview-packages/docs-ref-autogen/overview/Monitor.yml
:x:Error

Details

docs-ref-mapping/reference.yml
:warning:Warning

Details

preview-packages/docs-ref-mapping/reference.yml
:warning:Warning

Details

:warning:Warning

Details

preview-packages/docs-ref-autogen/overview/Monitor.yml

[Error: publish-conflict-url] File preview-packages/docs-ref-autogen/overview/Monitor.yml and docs-ref-services/preview/monitor.md being published to same url: /javascript/api/overview/azure/monitor with same moniker group: 375856b3fc964a4a3a6df8ce762619ce. Please retry building your content again. If the issue persists, please open a ticket in https://aka.ms/SiteHelp and include the URL of publishing report

docs-ref-mapping/reference.yml

Line 548, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingpage.services.durablefunctions'.
Line 735, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingpage.services.kusto'.
Line 916, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingpage.services.network'.
Line 944, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingpage.services.privatednsmanagement'.

preview-packages/docs-ref-mapping/reference.yml

Line 242, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingpage.services.network.pre'.

Line 0, Column 0: [Warning: redirected-file-not-removed - See documentation] Redirected file 'docs-ref-conceptual/index.md' are still in the repo. After adding a file to the redirection JSON file, you must delete the original file from the repo.
Line 0, Column 0: [Warning: output-path-conflict] Two or more files output to the same path 'javascript/dc3f00e56d73e509b7ade314d9c7f100/api/overview/azure/monitor.raw.page.json': 'docs-ref-autogen/overview/Monitor.yml [generated]', 'docs-ref-services/latest/monitor.md'.

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

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

File
Status
Preview URL
Details

preview-packages/docs-ref-autogen/overview/Monitor.yml
:x:Error

Details

docs-ref-mapping/reference.yml
:warning:Warning

Details

preview-packages/docs-ref-mapping/reference.yml
:warning:Warning

Details

:warning:Warning

Details

preview-packages/docs-ref-autogen/overview/Monitor.yml

[Error: publish-conflict-url] File preview-packages/docs-ref-autogen/overview/Monitor.yml and docs-ref-services/preview/monitor.md being published to same url: /javascript/api/overview/azure/monitor with same moniker group: 375856b3fc964a4a3a6df8ce762619ce. Please retry building your content again. If the issue persists, please open a ticket in https://aka.ms/SiteHelp and include the URL of publishing report

docs-ref-mapping/reference.yml

Line 548, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingpage.services.durablefunctions'.
Line 735, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingpage.services.kusto'.
Line 916, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingpage.services.network'.
Line 944, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingpage.services.privatednsmanagement'.

preview-packages/docs-ref-mapping/reference.yml

Line 242, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingpage.services.network.pre'.

Line 0, Column 0: [Warning: redirected-file-not-removed - See documentation] Redirected file 'docs-ref-conceptual/index.md' are still in the repo. After adding a file to the redirection JSON file, you must delete the original file from the repo.
Line 0, Column 0: [Warning: output-path-conflict] Two or more files output to the same path 'javascript/dc3f00e56d73e509b7ade314d9c7f100/api/overview/azure/monitor.raw.page.json': 'docs-ref-autogen/overview/Monitor.yml [generated]', 'docs-ref-services/latest/monitor.md'.

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

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

File
Status
Preview URL
Details

preview-packages/docs-ref-autogen/overview/Monitor.yml
:x:Error

Details

docs-ref-mapping/reference.yml
:warning:Warning

Details

preview-packages/docs-ref-mapping/reference.yml
:warning:Warning

Details

:warning:Warning

Details

preview-packages/docs-ref-autogen/overview/Monitor.yml

[Error: publish-conflict-url] File preview-packages/docs-ref-autogen/overview/Monitor.yml and docs-ref-services/preview/monitor.md being published to same url: /javascript/api/overview/azure/monitor with same moniker group: 375856b3fc964a4a3a6df8ce762619ce. Please retry building your content again. If the issue persists, please open a ticket in https://aka.ms/SiteHelp and include the URL of publishing report

docs-ref-mapping/reference.yml

Line 548, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingpage.services.durablefunctions'.
Line 735, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingpage.services.kusto'.
Line 916, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingpage.services.network'.
Line 944, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingpage.services.privatednsmanagement'.

preview-packages/docs-ref-mapping/reference.yml

Line 242, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingpage.services.network.pre'.

Line 0, Column 0: [Warning: redirected-file-not-removed - See documentation] Redirected file 'docs-ref-conceptual/index.md' are still in the repo. After adding a file to the redirection JSON file, you must delete the original file from the repo.
Line 0, Column 0: [Warning: output-path-conflict] Two or more files output to the same path 'javascript/dc3f00e56d73e509b7ade314d9c7f100/api/overview/azure/monitor.raw.page.json': 'docs-ref-autogen/overview/Monitor.yml [generated]', 'docs-ref-services/latest/monitor.md'.

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

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

File
Status
Preview URL
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-latest)
Details

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

<EMAIL_ADDRESS>
Line 5, Column 48: [Warning: xref-not-found] Cross reference not found: 'ErrorBar'.

<EMAIL_ADDRESS>
Line 5, Column 84: [Warning: xref-not-found] Cross reference not found: 'CallAdapter'.

<EMAIL_ADDRESS>
Line 5, Column 84: [Warning: xref-not-found] Cross reference not found: 'ChatAdapter'.

<EMAIL_ADDRESS>
Line 5, Column 24: [Warning: xref-not-found] Cross reference not found: 'createAzureCommunicationMeetingAdapter'.

<EMAIL_ADDRESS>
Line 5, Column 10: [Warning: xref-not-found] Cross reference not found: 'CallComposite'.

<EMAIL_ADDRESS>
Line 5, Column 57: [Warning: xref-not-found] Cross reference not found: 'StatefulCallClient'.
Line 7, Column 37: [Warning: xref-not-found] Cross reference not found: 'DeviceManagerState'.
Line 25, Column 23: [Warning: xref-not-found] Cross reference not found: '@azure/communication-calling#CallAgent'.
Line 25, Column 90: [Warning: xref-not-found] Cross reference not found: 'CallAgentState'.
Line 40, Column 23: [Warning: xref-not-found] Cross reference not found<EMAIL_ADDRESS>Line 40, Column 109: [Warning: xref-not-found] Cross reference not found: 'CallState'.
Line 41, Column 16: [Warning: xref-not-found] Cross reference not found<EMAIL_ADDRESS>Line 42, Column 1: [Warning: xref-not-found] Cross reference not found<EMAIL_ADDRESS>Line 43, Column 1: [Warning: xref-not-found] Cross reference not found: '@azure/communication-calling#Call'.
Line 65, Column 22: [Warning: xref-not-found] Cross reference not found<EMAIL_ADDRESS>Line 65, Column 81: [Warning: xref-not-found] Cross reference not found: 'CallState'.
Line 66, Column 6: [Warning: xref-not-found] Cross reference not found: 'MAX_CALL_HISTORY_LENGTH'.
Line 85, Column 23: [Warning: xref-not-found] Cross reference not found: '@azure/communication-calling#DeviceManager'.
Line 85, Column 94: [Warning: xref-not-found] Cross reference not found: 'DeviceManagerState'.
Line 100, Column 23: [Warning: xref-not-found] Cross reference not found: '@azure/communication-calling#IncomingCall'.
Line 100, Column 96: [Warning: xref-not-found] Cross reference not found: 'IncomingCall'.
Line 101, Column 16: [Warning: xref-not-found] Cross reference not found<EMAIL_ADDRESS>Line 120, Column 28: [Warning: xref-not-found] Cross reference not found<EMAIL_ADDRESS>Line 120, Column 87: [Warning: xref-not-found] Cross reference not found: 'IncomingCall'.
Line 121, Column 6: [Warning: xref-not-found] Cross reference not found: 'MAX_CALL_HISTORY_LENGTH'.
Line 158, Column 55: [Warning: xref-not-found] Cross reference not found: 'StatefulCallClient'.
Line 159, Column 83: [Warning: xref-not-found] Cross reference not found: 'StatefulCallClient'.

<EMAIL_ADDRESS>
Line 5, Column 40: [Warning: xref-not-found] Cross reference not found: 'CallComposite'.

<EMAIL_ADDRESS>
Line 5, Column 20: [Warning: xref-not-found] Cross reference not found: 'CallComposite'.
Line 118, Column 70: [Warning: xref-not-found] Cross reference not found: 'CallComposite'.

<EMAIL_ADDRESS>
Line 5, Column 30: [Warning: xref-not-found] Cross reference not found: 'CallComposite'.

<EMAIL_ADDRESS>
Line 5, Column 32: [Warning: xref-not-found] Cross reference not found: '@azure/communication-calling#Call'.
Line 5, Column 80: [Warning: xref-not-found] Cross reference not found: 'StatefulCallClient'.
Line 6, Column 58: [Warning: xref-not-found] Cross reference not found: 'StatefulCallClient'.
Line 20, Column 23: [Warning: xref-not-found] Cross reference not found<EMAIL_ADDRESS>Line 33, Column 23: [Warning: xref-not-found] Cross reference not found<EMAIL_ADDRESS>Line 59, Column 23: [Warning: xref-not-found] Cross reference not found<EMAIL_ADDRESS>Line 102, Column 23: [Warning: xref-not-found] Cross reference not found<EMAIL_ADDRESS>Line 115, Column 23: [Warning: xref-not-found] Cross reference not found<EMAIL_ADDRESS>Line 128, Column 23: [Warning: xref-not-found] Cross reference not found<EMAIL_ADDRESS>Line 141, Column 23: [Warning: xref-not-found] Cross reference not found<EMAIL_ADDRESS>Line 154, Column 23: [Warning: xref-not-found] Cross reference not found: '@azure/communication-calling#RecordingCallFeature'.
Line 167, Column 23: [Warning: xref-not-found] Cross reference not found<EMAIL_ADDRESS>Line 168, Column 13: [Warning: xref-not-found] Cross reference not found: 'RemoteParticipant'.
Line 168, Column 64: [Warning: xref-not-found] Cross reference not found: 'RemoteParticipantState.identifier'.
Line 169, Column 23: [Warning: xref-not-found] Cross reference not found: 'RemoteParticipantState.identifier'.
Line 170, Column 1: [Warning: xref-not-found] Cross reference not found: '@azure/communication-react#toFlatCommunicationIdentifier'.
Line 192, Column 13: [Warning: xref-not-found] Cross reference not found: 'RemoteParticipant'.
Line 192, Column 64: [Warning: xref-not-found] Cross reference not found: 'RemoteParticipantState.identifier'.
Line 193, Column 23: [Warning: xref-not-found] Cross reference not found: 'RemoteParticipantState.identifier'.
Line 194, Column 1: [Warning: xref-not-found] Cross reference not found: '@azure/communication-react#toFlatCommunicationIdentifier'.
Line 216, Column 73: [Warning: xref-not-found] Cross reference not found: 'CallState.remoteParticipants'.
Line 259, Column 23: [Warning: xref-not-found] Cross reference not found<EMAIL_ADDRESS>Line 272, Column 23: [Warning: xref-not-found] Cross reference not found: '@azure/communication-calling#TranscriptionCallFeature'.
Line 289, Column 23: [Warning: xref-not-found] Cross reference not found: '@azure/communication-calling#TransferCallFeature'.
Line 290, Column 1: [Warning: xref-not-found] Cross reference not found: 'TransferCallFeatureState'.

<EMAIL_ADDRESS>
Line 5, Column 26: [Warning: xref-not-found] Cross reference not found: 'usePropsFor'.

<EMAIL_ADDRESS>
Line 5, Column 28: [Warning: xref-not-found] Cross reference not found: 'CameraButton'.

<EMAIL_ADDRESS>
Line 5, Column 10: [Warning: xref-not-found] Cross reference not found: 'ChatComposite'.

<EMAIL_ADDRESS>
Line 5, Column 41: [Warning: xref-not-found] Cross reference not found: 'ChatClientState'.

<EMAIL_ADDRESS>
Line 5, Column 36: [Warning: xref-not-found] Cross reference not found: 'ChatClientProvider'.

<EMAIL_ADDRESS>
Line 5, Column 32: [Warning: xref-not-found] Cross reference not found: '@azure/communication-chat#ChatClient'.

<EMAIL_ADDRESS>
Line 5, Column 35: [Warning: xref-not-found] Cross reference not found: 'StatefulChatClient'.

<EMAIL_ADDRESS>
Line 7, Column 5: [Warning: xref-not-found] Cross reference not found: 'useHandlers'.
Line 7, Column 28: [Warning: xref-not-found] Cross reference not found: 'usePropsFor'.

<EMAIL_ADDRESS>
Line 5, Column 26: [Warning: xref-not-found] Cross reference not found: '@azure/communication-chat#ChatMessage'.

<EMAIL_ADDRESS>
Line 5, Column 28: [Warning: xref-not-found] Cross reference not found: 'ParticipantList'.

<EMAIL_ADDRESS>
Line 5, Column 26: [Warning: xref-not-found] Cross reference not found: 'usePropsFor'.

<EMAIL_ADDRESS>
Line 5, Column 36: [Warning: xref-not-found] Cross reference not found: 'ChatThreadClientProvider'.

<EMAIL_ADDRESS>
Line 5, Column 32: [Warning: xref-not-found] Cross reference not found: '@azure/communication-chat#ChatThreadClient'.

<EMAIL_ADDRESS>
Line 5, Column 32: [Warning: xref-not-found] Cross reference not found: '@azure/communication-calling#CallClient'.
Line 5, Column 88: [Warning: xref-not-found] Cross reference not found: '@azure/communication-chat#ChatClient'.
Line 6, Column 11: [Warning: xref-not-found] Cross reference not found: 'CallClientState'.
Line 6, Column 35: [Warning: xref-not-found] Cross reference not found: 'ChatClientState'.

<EMAIL_ADDRESS>
Line 5, Column 26: [Warning: xref-not-found] Cross reference not found: 'usePropsFor'.

<EMAIL_ADDRESS>
Line 5, Column 34: [Warning: xref-not-found] Cross reference not found: 'ControlBar'.

<EMAIL_ADDRESS>
Line 5, Column 20: [Warning: xref-not-found] Cross reference not found: 'ControlBar'.
Line 23, Column 15: [Warning: xref-not-found] Cross reference not found: 'React.ReactNode'.

<EMAIL_ADDRESS>
Line 5, Column 23: [Warning: xref-not-found] Cross reference not found: 'CallAdapterSubscribers'.

<EMAIL_ADDRESS>
Line 6, Column 35: [Warning: xref-not-found] Cross reference not found: 'usePropsFor'.

<EMAIL_ADDRESS>
Line 5, Column 20: [Warning: xref-not-found] Cross reference not found: 'ErrorBar'.
Line 6, Column 31: [Warning: xref-not-found] Cross reference not found: 'ErrorBar'.
Line 7, Column 1: [Warning: xref-not-found] Cross reference not found: '@fluentui/react#IMessageBarProps'.
Line 7, Column 65: [Warning: xref-not-found] Cross reference not found: '@fluentui/react#MessageBar'.

<EMAIL_ADDRESS>
Line 5, Column 28: [Warning: xref-not-found] Cross reference not found: 'ErrorBar'.

<EMAIL_ADDRESS>
Line 5, Column 20: [Warning: xref-not-found] Cross reference not found: 'GridLayout'.
Line 23, Column 15: [Warning: xref-not-found] Cross reference not found: 'React.ReactNode'.

<EMAIL_ADDRESS>
Line 5, Column 10: [Warning: xref-not-found] Cross reference not found: 'HorizontalGallery'.
Line 23, Column 15: [Warning: xref-not-found] Cross reference not found: 'React.ReactNode'.

<EMAIL_ADDRESS>
Line 5, Column 10: [Warning: xref-not-found] Cross reference not found: 'HorizontalGallery'.

<EMAIL_ADDRESS>
Line 5, Column 24: [Warning: xref-not-found] Cross reference not found: 'MessageThreadProps.onRenderJumpToNewMessageButton'.

<EMAIL_ADDRESS>
Line 5, Column 22: [Warning: xref-not-found] Cross reference not found: 'DiagnosticChangedEventListner'.

<EMAIL_ADDRESS>
Line 6, Column 5: [Warning: xref-not-found] Cross reference not found: 'MessageRenderer'.

<EMAIL_ADDRESS>
Line 5, Column 20: [Warning: xref-not-found] Cross reference not found: 'MessageThread'.

<EMAIL_ADDRESS>
Line 5, Column 28: [Warning: xref-not-found] Cross reference not found: 'MessageThread'.

<EMAIL_ADDRESS>
Line 5, Column 21: [Warning: xref-not-found] Cross reference not found: 'MessageThread'.

<EMAIL_ADDRESS>
Line 5, Column 28: [Warning: xref-not-found] Cross reference not found: 'MessageThread'.

<EMAIL_ADDRESS>
Line 5, Column 28: [Warning: xref-not-found] Cross reference not found: 'MicrophoneButton'.

<EMAIL_ADDRESS>
Line 5, Column 22: [Warning: xref-not-found] Cross reference not found: 'DiagnosticChangedEventListner'.

<EMAIL_ADDRESS>
Line 5, Column 28: [Warning: xref-not-found] Cross reference not found: 'OptionsButton'.

<EMAIL_ADDRESS>
Line 5, Column 21: [Warning: xref-not-found] Cross reference not found: 'ParticipantItem'.

<EMAIL_ADDRESS>
Line 5, Column 28: [Warning: xref-not-found] Cross reference not found: 'ParticipantList'.

<EMAIL_ADDRESS>
Line 5, Column 28: [Warning: xref-not-found] Cross reference not found: 'ParticipantsButton'.

<EMAIL_ADDRESS>
Line 5, Column 28: [Warning: xref-not-found] Cross reference not found: 'ScreenShareButton'.

<EMAIL_ADDRESS>
Line 5, Column 28: [Warning: xref-not-found] Cross reference not found: 'SendBox'.

<EMAIL_ADDRESS>
Line 5, Column 28: [Warning: xref-not-found] Cross reference not found: 'Sendbox'.

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

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

File
Status
Preview URL
Details

:x:Error

Details

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

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

Docs Build status updates of commit 52ba735:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-mapping/reference.yml
:warning:Warning

Details

preview-packages/docs-ref-mapping/reference.yml
:warning:Warning

Details

docs-ref-mapping/reference-unified.yml
:white_check_mark:Succeeded

docs-ref-services/latest/monitor.md
:white_check_mark:Succeeded
View (azure-node-latest)

previous-packages/docs-ref-mapping/reference.yml
:white_check_mark:Succeeded

docs-ref-mapping/reference.yml

Line 548, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingpage.services.durablefunctions'.
Line 735, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingpage.services.kusto'.
Line 895, Column 12: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingPage.services.monitor.Management'.
Line 916, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingpage.services.network'.
Line 944, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingpage.services.privatednsmanagement'.

preview-packages/docs-ref-mapping/reference.yml

Line 248, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingpage.services.network.pre'.

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

@danieljurek Can you review this, I updated with all the information required?

Docs Build status updates of commit 65ccb20:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-mapping/reference.yml
:warning:Warning

Details

preview-packages/docs-ref-mapping/reference.yml
:warning:Warning

Details

docs-ref-mapping/reference-unified.yml
:white_check_mark:Succeeded

docs-ref-services/latest/monitor.md
:white_check_mark:Succeeded
View (azure-node-latest)

previous-packages/docs-ref-mapping/reference.yml
:white_check_mark:Succeeded

docs-ref-mapping/reference.yml

Line 548, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingpage.services.durablefunctions'.
Line 735, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingpage.services.kusto'.
Line 894, Column 12: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingPage.services.monitor.Management'.
Line 915, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingpage.services.network'.
Line 943, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingpage.services.privatednsmanagement'.

preview-packages/docs-ref-mapping/reference.yml

Line 268, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingpage.services.network.pre'.

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

Docs Build status updates of commit 800fe9c:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-mapping/reference.yml
:warning:Warning

Details

preview-packages/docs-ref-mapping/reference.yml
:warning:Warning

Details

.vscode/launch.json
:white_check_mark:Succeeded

docs-ref-mapping/reference-unified.yml
:white_check_mark:Succeeded

docs-ref-services/latest/monitor.md
:white_check_mark:Succeeded
View (azure-node-latest)

previous-packages/docs-ref-mapping/reference.yml
:white_check_mark:Succeeded

docs-ref-mapping/reference.yml

Line 548, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingpage.services.durablefunctions'.
Line 735, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingpage.services.kusto'.
Line 894, Column 12: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingPage.services.monitor.Management'.
Line 915, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingpage.services.network'.
Line 943, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingpage.services.privatednsmanagement'.

preview-packages/docs-ref-mapping/reference.yml

Line 268, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingpage.services.network.pre'.

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

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

File
Status
Preview URL
Details

docs-ref-mapping/reference.yml
:warning:Warning

Details

preview-packages/docs-ref-mapping/reference.yml
:warning:Warning

Details

.vscode/launch.json
:white_check_mark:Succeeded

docs-ref-mapping/reference-unified.yml
:white_check_mark:Succeeded

docs-ref-services/latest/monitor.md
:white_check_mark:Succeeded
View (azure-node-latest)

previous-packages/docs-ref-mapping/reference.yml
:white_check_mark:Succeeded

docs-ref-mapping/reference.yml

Line 548, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingpage.services.durablefunctions'.
Line 735, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingpage.services.kusto'.
Line 894, Column 12: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingPage.services.monitor.Management'.
Line 915, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingpage.services.network'.
Line 943, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingpage.services.privatednsmanagement'.

preview-packages/docs-ref-mapping/reference.yml

Line 268, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingpage.services.network.pre'.

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

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

File
Status
Preview URL
Details

docs-ref-mapping/reference.yml
:warning:Warning

Details

preview-packages/docs-ref-mapping/reference.yml
:warning:Warning

Details

.vscode/launch.json
:white_check_mark:Succeeded

docs-ref-mapping/reference-unified.yml
:white_check_mark:Succeeded

docs-ref-services/latest/monitor.md
:white_check_mark:Succeeded
View (azure-node-latest)

previous-packages/docs-ref-mapping/reference.yml
:white_check_mark:Succeeded

docs-ref-mapping/reference.yml

Line 548, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingpage.services.durablefunctions'.
Line 735, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingpage.services.kusto'.
Line 894, Column 12: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingPage.services.monitor.Management'.
Line 915, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingpage.services.network'.
Line 943, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingpage.services.privatednsmanagement'.

preview-packages/docs-ref-mapping/reference.yml

Line 268, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingpage.services.network.pre'.

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

@scbedd I updated the PR

Docs Build status updates of commit 53aee78:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-mapping/reference.yml
:warning:Warning

Details

preview-packages/docs-ref-mapping/reference.yml
:warning:Warning

Details

.vscode/launch.json
:white_check_mark:Succeeded

docs-ref-mapping/reference-unified.yml
:white_check_mark:Succeeded

docs-ref-services/latest/monitor.md
:white_check_mark:Succeeded
View (azure-node-latest)

previous-packages/docs-ref-mapping/reference.yml
:white_check_mark:Succeeded

docs-ref-mapping/reference.yml

Line 548, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingpage.services.durablefunctions'.
Line 735, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingpage.services.kusto'.
Line 894, Column 12: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingPage.services.monitor.Management'.
Line 915, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingpage.services.network'.
Line 943, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingpage.services.privatednsmanagement'.

preview-packages/docs-ref-mapping/reference.yml

Line 268, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingpage.services.network.pre'.

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

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

File
Status
Preview URL
Details

docs-ref-mapping/reference.yml
:warning:Warning

Details

preview-packages/docs-ref-mapping/reference.yml
:warning:Warning

Details

docs-ref-mapping/reference-unified.yml
:white_check_mark:Succeeded

docs-ref-services/latest/monitor.md
:white_check_mark:Succeeded
View (azure-node-latest)

previous-packages/docs-ref-mapping/reference.yml
:white_check_mark:Succeeded

docs-ref-mapping/reference.yml

Line 548, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingpage.services.durablefunctions'.
Line 735, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingpage.services.kusto'.
Line 894, Column 12: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingPage.services.monitor.Management'.
Line 915, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingpage.services.network'.
Line 943, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingpage.services.privatednsmanagement'.

preview-packages/docs-ref-mapping/reference.yml

Line 268, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingpage.services.network.pre'.

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

Docs Build status updates of commit 207e191:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-mapping/reference.yml
:warning:Warning

Details

preview-packages/docs-ref-mapping/reference.yml
:warning:Warning

Details

docs-ref-mapping/reference-unified.yml
:white_check_mark:Succeeded

docs-ref-services/latest/monitor.md
:white_check_mark:Succeeded
View (azure-node-latest)

previous-packages/docs-ref-mapping/reference.yml
:white_check_mark:Succeeded

docs-ref-mapping/reference.yml

Line 548, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingpage.services.durablefunctions'.
Line 735, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingpage.services.kusto'.
Line 896, Column 12: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingPage.services.monitor.Management'.
Line 917, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingpage.services.network'.
Line 945, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingpage.services.privatednsmanagement'.

preview-packages/docs-ref-mapping/reference.yml

Line 295, Column 10: [Warning: xref-not-found] Cross reference not found: 'azure.nodejs.sdk.landingpage.services.network.pre'.

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


Rename cofree/envt/free/coenvt to easier attr names

I'm a tiny (very tiny) bit sad about losing the more "proper" names for these concepts. However, I think the increased readability and decrease in cognitive overhead (remember the different parameter order and different names!) is a nice win.
Addresses #56
I'd like to cut a 0.5.0 release once this change is merged.

woo accessibility!


WiFi Taking Between 3 to 5 Minutes to Initiate

I’ve managed to successfully employ the single board RPIsolution to my Tesla Model S. I’m using f RPi4 with 4GB of RAM but it’s currently taking anywhere between 3 to 5 minutes before the WiFi is seen by the Model S and becomes stable (it appears intermittently after a couple of minutes but will not accept the password and then disappears again). Is this normal behaviour?

Have you got the latest PI firmware?

Yes.

I also have a longer than expected startup time, but I am in no position to know if this is expected behaviour or not.  Also on latest Pi f/w

I have the same issue. However perhaps theses known to the developer. The instructions say if you cannot connect to the wifi, leave the pie on for 10-15 minutes and try again.
"If you are not able to connect to Wi-Fi after installing Tesla Android:
Leave the board powered on for a few minutes(10, 15) after the first boot (the boot sequence is completed when the Wi-Fi network becomes available)
Reboot the board by unplugging the USB-C cable
Try again
"


Please consider adding your adapter to the official iobroker repository.

Please consider adding your adapter to the official iobroker repository. For details see here:
https://github.com/ioBroker/ioBroker.repositories#add-a-new-adapter-to-the-latest-repository

Sorry, just detected that this is already initiated.


"Initial connection" randomly fails on Edge (Win11, with Docker + WSL2). Works on Firefox.

After setting up Superset in WSL2 environment with Docker, everything works as expected on Firefox browser. However, on Edge, it randomly fails to connect with "Initial connection" never finishing. I have never had similar problems with Edge before, so I am creating issue here, even it may not be related to Superset.
How to reproduce the bug

Install Superset on Windows 11 with latest updates, Docker, WSL2, and Ubuntu distro setup. (from master branch)
Start Edge browser (latest Version 97.0.1072.69)
Open http://localhost:8088
Login with admin:admin credentials and start browsing

Expected results
Everything works
Actual results
Around 40% (subjective) of network requests fails during "Initial connection" phase. Please see screenshot.
If I switch to other browser (e.g. Firefox), problem is gone.
Nothing in docker logs, as these failed requests don't reach app. Only reason I am creating this issue is because I haven't had similar problems with Edge on any other Docker based projects/environments I am using.
Screenshots

Environment
(please complete the following information):

Edge browser (latest Version 97.0.1072.69)
superset version: Docker container reports: Superset 0.0.0dev. But I am using image apache/superset  pulled on Jan25`22
Launched from docker environment with docker-compose-non-dev.yml

Checklist
Make sure to follow these steps before submitting your issue - thank you!

[X] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[X] I have reproduced the issue with at least the latest released version of superset.
[X] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context

Hey @acirulis as a heads up, WSL isn't a testing target for Superset (although we generally expect things to "just work" because it's WSL is trying to mirror a Ubuntu environment). Neither is Microsoft Edge, but again in theory it should be similar to Chrome because of the underlying engine choice.
Re: 0.0.0dev you're spot on that this just means you're using a non-versioned release. It's an attempt to follow semantic versioning protocol but essentially convey "dev" version.
Without logs or errors, this is going to be super hard to replicate. Let us know if you're able to interrogate this further or if you come up with any other hints that allow someone else to replicate this and maybe fix this. Of course, we'd also appreciate your contribution here as well :)

Ok, so I decided to try Chrome as well, since it uses same engine as Edge. The problem was even worse. Then I found https://github.com/microsoft/WSL/issues/4340 which seems related - after switching from http://localhost to http://<IP_ADDRESS> or http://my-custom-hostname.local.io problem disappeared. I guess problem is hidden somewhere in between browser / WSL / webserver (Flask) connections. I will be closing the issue for now but maybe it will help somebody with same problem.


Added secondary light to 3D Advanced Import Settings

Added a second light for the 3D Preview Viewport and UI toggle buttons which resemble the ones in the EditorMaterialPreviewPlugin
On branch add_secondary_light_to_3d_resource_importer
Changes to be committed:
modified:   editor/import/scene_import_settings.cpp
modified:   editor/import/scene_import_settings.h

Bugsquad edit: This closes https://github.com/godotengine/godot-proposals/issues/6707.

Tested. I noticed that the two lights are coming from similar angles, one more on top and one more on the side. However, the material preview has light coming from very different angles, one light in the bottom and one light in the top right. Since one of the goals is to resemble that editor, shouldn't one of the lights be coming from below?
Also, in the material preview, the lights stay fixed relative to the camera. In this PR, the lights are fixed relative to the object. I think it would be better to have lights fixed relative to the camera, so you can view different parts of the model illuminated by the light at different angles relative to the model, instead of having a fixed part of the model lit at the same angle relative to the model.

Since the original author was inactive, I sent them an email asking for write access to their repo so I can push to their PRs, which they granted to me. I have taken over this PR in order to bring it to the finish line. Most of the code is still Jeronimo's work, which is itself kept very similar to the mesh and material previewer code, so I have him marked as author.
I made the following changes to this PR:

Rebase and fix conflicts.
In a few minor ways, make the code more similar to the mesh and material previewers.
Introduce a new method to Node3D called set_as_top_level_keep_local, which is like set_as_top_level but simpler, as it excludes the code that preserves the global transform (instead, it preserves the local transform).
Implement both points in my comment above.

The light directions are now the same as the mesh and material previewers.
The lights are now fixed relative to the camera by default, for consistency with the mesh and material previews.

However, if you prefer the old behavior for consistency with an orbiting camera in the scene editor, that is also kept. There is now a button in the top-right that will toggle between the rotation modes:

This new button uses a new icon called "PreviewRotate", which is the same as "ToolRotate" but with an outline and brighter (thank you to @MewPurPur for making this).

Thanks!


IE 9 custom headers

Is there any work around for adding custom headers with IE 9?

pass them as request url parameter or fields

Awesome, thanks for the help!


Catastrophic - CatAI is completely broken (Segmentation fault core dumped fatal error)

Spinning off into it's own issue.
Please refer to the troubleshooting before opening an issue. You might find the solution there.
Describe the bug
CatAI after updating with the advice on issue #29 now no longer starts up at all, and tosses a segmentation fault. The errors produced when trying to start CatAI are the following:
<EMAIL_ADDRESS>start
node src/index.js --production true --ui catai
Segmentation fault (core dumped)
Using catai update results into a different error, but same outcome
fatal runtime error: Rust cannot catch foreign exceptions
Aborted (core dumped)
fatal runtime error: Rust cannot catch foreign exceptions
Aborted (core dumped)
at file:///home/thesystemguy/.nvm/versions/node/v20.2.0/lib/node_modules/catai/scripts/cli.js:69:27
exit code: 134 (Process aborted)
Reinstallation does the same thing as using catai update. This is a showstopper problem.
Desktop (please complete the following information):
OS: Linux Mint 21.2 Cinnamon, Linux 5.15.0-76-generic
Browser: n/a (no start)
CatAI version 1.0.2 (as advised in issue #29)
Node.js version v18.16.0
CPU: AMD Ryzen 5 5600H with Radeon Graphics
RAM: 30.7 GiB (512 MiB reserved to graphics chipset)

Version 1, is unstable and therefore in preview.
You can downgrade to version 0 with:
npm -g i catai@0

Then install one of the support models in this version

What about 0.9? I want the last version before 0.9 as I use GPT4freeOn Jul 19, 2023, at 7:15 AM, Ido S. @.> wrote:
Version 1, is unstable and therefore in preview.
You can downgrade to version 0 with:
npm -g i @.
Then install one of the support models in this version
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

Downgrading does not help. I'm still getting the same error, even after downgrading straight to 0.3.12

That may be because you use an unsupported model, use 'catai install' to install one of the supported models

I'm facing same error on local run.
I use Windows 10, node.js v19.9.0
catai commit 4bed6183b764fce9b353b750c595a0f687dc85ec
$ npm start
><EMAIL_ADDRESS>start
> node src/index.js

/c/Program Files/nodejs/npm: line 44:  3625 Segmentation fault      "$NODE_EXE" "$NPM_CLI_JS" "$@"

This software is more or less abandonware and isn’t being properly supported. Migrate to LocalAI or AutoGPT4allOn Jul 23, 2023, at 5:41 PM, pavelpiha @.***> wrote:
I'm facing same error on local run.
I use Windows 10, node.js v19.9.0
catai commit 4bed618
$ npm start

@.*** start
node src/index.js

/c/Program Files/nodejs/npm: line 44:  3625 Segmentation fault      "$NODE_EXE" "$NPM_CLI_JS" "$@"
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

The library that binds CatAI with the model, stopped getting updates (node-llama). Now I am implementing, something like that, but this can take a while. For the meantime only old GGML will be supported :(

Thank you for the response. Perhaps I'm trying to run it locally from cloned repository as written in Development
Could you possibly suggest which commit should I checkout?

You only need to downgrade the node-llama packages to version 1.5, and this should work

Yes, Just did it. Fixed it by reverting package-lock.json  in catai/server. Looks like problem in dependencies.

This software is abandonware and relies on complicated package nonsense. Please consider using C++ or x86 assembly instead of a volatile language like Python. Might be painful, but at least it guarantees it actually bloody works instead of breaking CPU NX policies and segfaulting into /dev/null.


No working with mosquitto on raspberry

Hi, i'm trying this sketch on an Arduino Uno with Ethernet shield:
include <SPI.h>
#include <Ethernet.h>
#define MQTT_VERSION 3
#include <PubSubClient.h>
char * mosquittoIP= "<IP_ADDRESS>";
byte mac[]    = {  0xDE, 0xED, 0xBA, 0xFE, 0xFE, 0xED };
IPAddress server(10,51,0,249);
EthernetClient ethClient;
PubSubClient client(mosquittoIP, 1883, 0, ethClient);

unsigned long lastMillis = 0;

void setup()
{
  Serial.begin(57600);
  while(Ethernet.begin(mac)==0){
  };
  Serial.println("CONNECTED TO LAN");
  if (ethClient.connect(server, 1883)) {
    Serial.println("mosquitto is reachable");
  } else {
    Serial.println("sure about IP?");
  }
}
String buildJson(){
  String json="{\"product_id\":";
  json+="\"20\"}";
  return json;
}
long lastUpdate=0;
void loop(){
   client.loop();
   if (!client.connected()) {
    Serial.print("Trying to connect to: ");
    Serial.println(mosquittoIP);
    client.connect("temperatureSensor") ;
   }
   if (client.connected()  && millis()-lastUpdate>5000) {
      lastUpdate=millis();
      Serial.println("CONNECTED TO mosquitto");
      String json = buildJson();
      char jsonStr [200];
      json.toCharArray(jsonStr,200);
      boolean pubresult = client.publish("sensor_logs",jsonStr);
      Serial.print("attempt to send ");
      Serial.println(jsonStr);
      if (pubresult)
        Serial.println("successfully sent");
      else
        Serial.println("unsuccessfully sent");
   } else if(!client.connected()){
      Serial.println("ERROR DURING CONNECTION WITH mosquitto");
      Serial.print("failed, rc=");
      Serial.println(client.state());
      delay(1000);
   }
}

I've a raspberry with mosquitto as server.
On Arduino the log is:
Trying to connect to: <IP_ADDRESS>
ERROR DURING CONNECTION WITH mosquitto
failed, rc=-2
Trying to connect to: <IP_ADDRESS>
ERROR DURING CONNECTION WITH mosquitto
failed, rc=-2
I've read other issues and try to connect via webclient example and it works.
I connect correctly from paho java plugin via tcp://<IP_ADDRESS>:1883

Solved... idk why but this broke communications.
if (ethClient.connect(server, 1883)) {
Serial.println("mosquitto is reachable");
} else {
Serial.println("sure about IP?");
}

I suspect creating a tcp connection to the broker and leaving it open would cause issues when the PubSubClient attempts to create it's own connection. Glad you got it working.


Important Checkboxes in Issues template

Current

Only code of conduct checkbox is present in issue temp

Change

If there are checkboxes like GSSOC'23 it will make labeling easier for project admins

Not Needed


Add new CLI for creating metadata cubes

Addresses #1273 / Closes #1273

Add CLI, generate-metadata-cube, for accepting input to create metadata cube as per the users specification.
Add generate_metadata() function which processes the values provided accordingly to pass to either set_up_variable_cube, set_up_percentile_cube or set_up_probability_cube. Function parameters allow for: specification of domain and grid setup; setting realizations and height/pressure levels; creating a variable cube, percentile cube or probability cube; specifying time data. Returns the resulting cube.
Create tests to test generate_metadata
Create acceptance tests for the CLI
Add sha256sums of new data to SHA256SUMS

Testing:

[x] Ran tests and they passed OK
[x] Added new tests for the new feature(s)

Acceptance test directory:   /data/users/vsmart/improver_tests/
New acceptance test data:   /data/users/vsmart/improver_tests/generate-metadata-cube/

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 9

Complexity increasing per file
==============================
- improver/cli/generate_metadata_cube.py  11
- improver_tests/acceptance/test_generate_metadata_cube.py  2
- improver_tests/synthetic_data/test_generate_metadata.py  19
- improver/synthetic_data/generate_metadata.py  13

Clones added
============
- improver_tests/synthetic_data/test_generate_metadata.py  4

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 4

Complexity increasing per file
==============================
- improver/cli/generate_metadata_cube.py  11
- improver_tests/acceptance/test_generate_metadata_cube.py  2
- improver_tests/synthetic_data/test_generate_metadata.py  19
- improver/synthetic_data/generate_metadata.py  13

Clones added
============
- improver_tests/synthetic_data/test_generate_metadata.py  4

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 4

Complexity increasing per file
==============================
- improver/synthetic_data/generate_metadata.py  13
- improver_tests/acceptance/test_generate_metadata_cube.py  2
- improver_tests/synthetic_data/test_generate_metadata.py  19
- improver/cli/generate_metadata_cube.py  7

Clones added
============
- improver_tests/synthetic_data/test_generate_metadata.py  4

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 2

Complexity increasing per file
==============================
- improver/synthetic_data/generate_metadata.py  11
- improver_tests/acceptance/test_generate_metadata_cube.py  2
- improver_tests/synthetic_data/test_generate_metadata.py  19
- improver/cli/generate_metadata_cube.py  7

Clones added
============
- improver_tests/synthetic_data/test_generate_metadata.py  4

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 2

Complexity increasing per file
==============================
- improver/synthetic_data/generate_metadata.py  11
- improver/cli/generate_metadata_cube.py  7
- improver_tests/acceptance/test_generate_metadata_cube.py  2
- improver_tests/synthetic_data/test_generate_metadata.py  19

Clones added
============
- improver_tests/synthetic_data/test_generate_metadata.py  4

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 2

Complexity increasing per file
==============================
- improver_tests/acceptance/test_generate_metadata_cube.py  2
- improver/cli/generate_metadata_cube.py  7
- improver/synthetic_data/generate_metadata.py  11
- improver_tests/synthetic_data/test_generate_metadata.py  19

Clones added
============
- improver_tests/synthetic_data/test_generate_metadata.py  4

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 2

Complexity increasing per file
==============================
- improver/cli/generate_metadata_cube.py  7
- improver_tests/synthetic_data/test_generate_metadata.py  19
- improver/synthetic_data/generate_metadata.py  11
- improver_tests/acceptance/test_generate_metadata_cube.py  2

Clones added
============
- improver_tests/synthetic_data/test_generate_metadata.py  4

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 2

Complexity increasing per file
==============================
- improver_tests/synthetic_data/test_generate_metadata.py  19
- improver/synthetic_data/generate_metadata.py  11
- improver_tests/acceptance/test_generate_metadata_cube.py  2
- improver/cli/generate_metadata_cube.py  7

Clones added
============
- improver_tests/synthetic_data/test_generate_metadata.py  4

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 13

Complexity increasing per file
==============================
- improver_tests/synthetic_data/test_generate_metadata.py  19
- improver_tests/acceptance/test_generate_metadata_cube.py  2
- improver/cli/generate_metadata_cube.py  7
- improver/synthetic_data/generate_metadata.py  11

Clones added
============
- improver_tests/synthetic_data/test_generate_metadata.py  4

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 14

Complexity increasing per file
==============================
- improver_tests/synthetic_data/test_generate_metadata.py  19
- improver/cli/generate_metadata_cube.py  7
- improver/synthetic_data/generate_metadata.py  11
- improver_tests/acceptance/test_generate_metadata_cube.py  2

Clones added
============
- improver_tests/synthetic_data/test_generate_metadata.py  4

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 14

Complexity increasing per file
==============================
- improver_tests/acceptance/test_generate_metadata_cube.py  2
- improver/synthetic_data/generate_metadata.py  11
- improver/cli/generate_metadata_cube.py  7
- improver_tests/synthetic_data/test_generate_metadata.py  19

Clones added
============
- improver_tests/synthetic_data/test_generate_metadata.py  4

See the complete overview on Codacy


[Feature Request]Option to hide Health Bars

Title says it all really, an option to hide the Health Bar on tooltips would be cool :)

Added da53ea8817da4bce8322d9f5724e9e3e0542f03f


CopySpec.expand(Map) fails when map has only one entry

Expected Behavior
            project.copy {
                from("template.txt")
                into(...)
                expand(mapOf("templateVar" to "Some content"))
            }

The code above should succeed.
Current Behavior
The code fails with java.lang.UnsupportedOperationException (no error message), unless you add an extra dummy entry to the map, like expand(mapOf("templateVar" to "Some content", "dummy" to "blah")).
Steps to Reproduce
See Github project: https://github.com/birukoff/gradle-copy-bug

Create template file that uses only one variable.
Invoke copy operation with expand(Map). Pass a map with only one required entry there.
See the task fail.
Add a useless dummy entry into the map.
The task succeeds.

I found that problem in method mapOf. It returns a singleton map which is unmodifiable.
I wrote a test that throws the same java.lang.UnsupportedOperationException, and try to make a modifiable copy of properties org.gradle.api.internal.file.copy.FilterChain#expand.
But it's not working, because of groovy.text.SimpleTemplateEngine.SimpleTemplate#make(java.util.Map) uses these properties to write property with key 'out' that used in other parts of Gradle:
org.gradle.api.tasks.CopyTaskIntegrationSpec#useful help message when property cannot be expanded
org.gradle.api.tasks.CopyTaskIntegrationSpec#useful help message when property cannot be expanded in filter chain
org.gradle.api.tasks.CopyTaskIntegrationSpec#useful help message when property cannot be expanded in filter chain
I can create modifiable copy of properties in org.gradle.api.internal.file.copy.DefaultCopySpec#expand, but there are many places with similar signatures and possibly similar problems

I found that only one class makes real work in the expand method.

I wrote an integration test for this problem and fix in DefaultCopyDetails#expand

Seems this has been fixed by the linked PR.

I am still running into this error. Gradle is on 7.0.2, which seems to be the latest.
Offending Gradle config:
tasks.withType<ProcessResources> {
    val properties = mapOf("version" to project.version)

    inputs.properties(properties)

    filesMatching("version.properties") {
        expand(properties)
    }
}

With just this, I get
* What went wrong:
Execution failed for task ':ug-gradle-plugin:processResources'.
> Could not copy file '<snip>/src/main/resources/version.properties' to '<snip>/build/resources/main/version.properties'.
   > java.lang.UnsupportedOperationException (no error message)

If I add a gratuitous second entry to the map, it fails.


Init several molecule properties on crystaldata initialization

e.g., num atoms & molecule mass

Effectively covered in equivariant_implement - adjusted data class in general


node version issue

Unsupported engine for @0.1.0: wanted: {"node":">=14.x. <=16.x.x","npm":">=6.0.0"} (current: {"node":"14.19.2","npm":"6.14.17"})
intent with different versions 14 and 16 same error

Thanks for submitting this issue. Please update to v1.0.5 which also includes support for node 18 (in line with the current support by Strapi).


Tami4 integration stopped working

First the 'boiled water' button stopped working (once clicked it generated an error).
After few failed attempts I wanted to 're-install', the I deleted the integration and tried to install.
On the validation/verification process (SMS) -  after inputting the mobile number - "Unexpected error" is received (screenshot below).

Here is the log:
Logger: homeassistant.components.tami4.config_flow
Source: components/tami4/config_flow.py:46
integration: Tami4 Edge / Edge+ (documentation, issues)
First occurred: 8:08:17 AM (9 occurrences)
Last logged: 10:53:03 AM
Unexpected exception
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/tami4/config_flow.py", line 46, in async_step_user
await self.hass.async_add_executor_job(
File "/usr/local/lib/python3.12/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/Tami4EdgeAPI/Tami4EdgeAPI.py", line 215, in request_otp
if not response["success"]:
~~~~~~~~^^^^^^^^^^^
KeyError: 'success'

Hi, by looking at the logs attached in: https://github.com/home-assistant/core/issues/113167#issuecomment-2146682339
Looks like they changed the API.
I will fix it soon.

@Guy293 thanks guy
was about to post here, but saw that you responded already.

following

Thanks @Guy293 , Great integration 👍

I've released an update for Tami4EdgeAPI, version V3.0.
I am now working on pushing it to Home Assistant repo.

I've released an update for Tami4EdgeAPI, version v3.0. I am now working on pushing it to Home Assistant repo.

thank you Guy!
אין עליך!

I've opened a PR In home assistant, Y'all can help merging it faster by review it and adding a comment: https://github.com/home-assistant/core/pull/119158

@Guy293 which version of HA it will be released on? thought its part of 2024.6.2?

any update on this? its stiull not working ...

any update on this? its stiull not working ...

Seems like the latest home assistant version includes the fix

Hi Guy, I updated to the latest hass version and still encounter a problem. I get "Unknown error occurred" once I enter the code I get via SMS.

I am sure my phone number is registered since I am using the Tami4 app and I am sure I write the correct code into hass...
Here is the log:
Logger: root
Source: /usr/local/lib/python3.12/site-packages/Tami4EdgeAPI/Tami4EdgeAPI.py:251
First occurred: July 3, 2024 at 9:45:08 PM (3 occurrences)
Last logged: 7:39:21 AM
OTP Submission Failed, response: {'status': 403, 'message': 'invalid_grant', 'description': 'Wrong phone number or verification code.', 'timestamp': '2024-07-03T18:45:08Z'}
OTP Submission Failed, response: {'status': 403, 'message': 'invalid_grant', 'description': 'Wrong phone number or verification code.', 'timestamp': '2024-07-03T18:45:44Z'}
OTP Submission Failed, response: {'status': 403, 'message': 'invalid_grant', 'description': 'Wrong phone number or verification code.', 'timestamp': '2024-07-04T04:39:21Z'}


BE: KC: Fix connector listing with STOPPED state

[ ] Breaking change? (if so, please describe the impact and migration path for existing application instances)

What changes did you make? (Give an overview)
Fixes #510
Is there anything you'd like reviewers to focus on?
How Has This Been Tested? (put an "x" (case-sensitive!) next to an item)

[ ] No need to
[x] Manually (please, describe, if necessary)
[ ] Unit checks
[ ] Integration checks
[ ] Covered by existing automation

Checklist (put an "x" (case-sensitive!) next to all the items, otherwise the build will fail)

[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation (e.g. ENVIRONMENT VARIABLES)
[ ] My changes generate no new warnings (e.g. Sonar is happy)
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged

Check out Contributing and Code of Conduct
A picture of a cute animal (not mandatory but encouraged)

@developster thanks for your first contribution to kafbat UI!


Users with different email/username getting misidentified by umapi-client

There's a check in the UserAction class of umapi-client that tries to infer the user type:
        if username:
            if email and username.lower() == email.lower():
                # ignore the username if it's the same as the email (policy default)
                username = None
            elif id_type is not IdentityTypes.federatedID:
                raise ValueError("Username must match email except for Federated ID")
            else:
                self._validate(username=username)
                if domain:
                    self._validate(domain=domain)
                    self.domain = domain

Basically, if username is set and is different from the email of a user's record, then it assumes the federated auth type is username-based and validates the username accordingly.
A problem arises with certain Okta records that have username and email set to two different email addresses.  Because they differ, this check attempts to validate the username field, but that validation fails because username should not be a full email address.
Why are we getting two email addresses from Okta for certain users?  Which email address do we use for email ID?  We need to use the correct email ID address and make sure the username field is set to None.

Alternatively, the email field and username field should both be set to the email ID that sync will use to create/update the user record.

Resolved by leaving username field blank.


Nit: Rename session files to source

Signed-off-by: Bogdan Drutu<EMAIL_ADDRESS>

@bogdandrutu do you mind rebasing to pick up a windows test job fix?

@rmfitzpatrick done


[Feature](inverted index) index tool add match_all and match_phrase

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


broker: swap default broker from eats to http

Signed-off-by: Vasiliy Tolstov<EMAIL_ADDRESS>

@asim why we have Handle option in go-plugins/broker/http ? i don't see any usage of it

It was to enable adding a handler for things like prometheus

do we need this option too? i'm ask because this is not default broker option, but it exposed in broker package

may be move it to go-micro/broker/http ?

yea add the options

done

Merge?

waiting for ci


Rename MARGIN

As discussed in here https://github.com/microbiome/mia/pull/562 and here https://github.com/microbiome/mia/pull/556, our MARGIN parameter does not follow the common meaning in base R.
In base R, the MARGIN = 2 specifies that the operation is performed across each column, ensuring that the dimension where the operation is applied remains unchanged. However, in our methods, the dimension of the output can change.
> library(mia)
> data("GlobalPatterns")
> tse <- GlobalPatterns
> dim(tse)
[1] 19216    26
> temp <- apply(assay(tse), 2, sum)
> length(temp)
[1] 26
> temp <- agglomerateByVariable(tse, MARGIN = 2, f = "SampleType")
> dim(temp)
[1] 19216     9

This can be misleading if MARGIN has multiple meanings. However, changing the parameter value to the opposite (for example in the case of agglomerateByVariable) can also be unclear since the data container and functions are more complex (from where to find the variable that is used in merging?).
It is beneficial that we use common parameters in our system. That is why we should change the name of MARGIN to by.
MARGIN is used in several functions. Some of them are already in release (must be deprecated) and some are only in devel (can be removed without deprecation).

splitOn: release
agglomerateByVariable: devel
addCluster: release
transformAssay: release
getCrossAssociation: release

The usage could be look like this:

library(mia)

data("GlobalPatterns")
tse <- GlobalPatterns

# split by columns
temp <- splitOn(tse, f = "SampleType", by = "cols")

# Agglomerate by columns
temp <- agglomerateByVariable(tse, f = "SampleType", by = "columns")

# Cluster by columns
library(bluster)
tse <- addCluster(tse, by = "samples", HclustParam(metric = "bray", dist.fun = vegan::vegdist))

# transform by rows
tse <- transformAssay(tse, method = "z", by = "rows")

# correlate by rows
temp <- getCrossAssociation(tse[1:10, ], tse[1:10], by = 1)

The documentation should use values "cols" and "rows" but we could still support 1, 2, columns... etc. hiddenly since we have the util function .check_MARGIN
-Tuomas

As MARGIN is used in vegan::decostand, we have to still think about what to do with transformAssay and its MARGIN parameter, It does not violate the meaning of MARGIN in base R, so I think we could leave MARGIN in transformAssay as it is currently


Added DNS Server Listing and Zone Transfer

Added listing of DNS Servers and AXFR Zone Transfer referencing https://www.acunetix.com/blog/articles/dns-zone-transfers-axfr/

/merge

Allow merging

Defaults
CLIENT_ID='wm_id_zIPGbkEDB5Cv9dCzo7nS'
API_URI='https://webmaker-api.herokuapp.com'
LOGIN_URI='https://id.mofostaging.net'

👍

Hey there

Hello
El mar, 27 de jun de 2023, 5:55 p. m., Ifeojobe @.***>
escribió:

Hey there
—
Reply to this email directly, view it on GitHub
https://github.com/trimstray/the-book-of-secret-knowledge/pull/398#issuecomment-1610377643,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXJ46VGBYBZ2V5FC5SIHWATXNNXHZANCNFSM6AAAAAAYFR4TKE
.
You are receiving this because you commented.Message ID:
@.***>

Thanks.
## octocat

On Sun, Aug 13, 2023, 4:45 PM jeperson @.***> wrote:

@.**** approved this pull request.
—
Reply to this email directly, view it on GitHub
https://github.com/trimstray/the-book-of-secret-knowledge/pull/398#pullrequestreview-1575890489,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A54XQNR36PR7BTWKDD4JDR3XVE4F7ANCNFSM6AAAAAAYFR4TKE
.
You are receiving this because you commented.Message ID:
@.***
com>

<IP_ADDRESS>.1
Regards to f host.
Crash
On Sat, Jan 13, 2024, 6:52 AM README.md @.***> wrote:

@.**** commented on this pull request.
In README.md
https://github.com/trimstray/the-book-of-secret-knowledge/pull/398#discussion_r1451470404
:

@@ -3938,6 +3938,16 @@ dig google.com ANY +noall +answer

dig -x <IP_ADDRESS> +short

⬇ Suggested change

-dig -x <IP_ADDRESS> +short
+dig -x <IP_ADDRESS> +short

—
Reply to this email directly, view it on GitHub
<https://github.com/trimstray/the-book-of-secret-knowledge/pull/398#discussion_r1451470404>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AV4G3V5JK3PSGFLVCFMCK4LYOJYRDAVCNFSM6AAAAAAYFR4TKGVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTQMJZHE4DCMZRGE>
.
You are receiving this because you are subscribed to this thread.Message
ID: <trimstray/the-book-of-secret-knowledge/pull/398/review/1819981311@
github.com>

Added listing of DNS Servers and AXFR Zone Transfer referencing https://www.acunetix.com/blog/articles/dns-zone-transfers-axfr/

Pullout request change

Thanks.
## octocat

On Sun, Aug 13, 2023, 4:45 PM jeperson @.***> wrote:

@.**** approved this pull request.
—
Reply to this email directly, view it on GitHub
https://github.com/trimstray/the-book-of-secret-knowledge/pull/398#pullrequestreview-1575890489,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A54XQNR36PR7BTWKDD4JDR3XVE4F7ANCNFSM6AAAAAAYFR4TKE
.
You are receiving this because you commented.Message ID:
@.***
com>


Update Set-VpnConnectionProxy.md

Adding additional information for the scope / limitation of the VPN proxy settings configuration

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

File
Status
Preview URL
Details

docset/windows/vpnclient/Set-VpnConnectionProxy.md
:white_check_mark:Succeeded

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 81aef52:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/windows/vpnclient/Set-VpnConnectionProxy.md
:white_check_mark:Succeeded

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 be39b3a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/windows/vpnclient/Set-VpnConnectionProxy.md
:white_check_mark:Succeeded

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

@JohanFreelancer9 Copy editing is needed for this PR. Thanks.

@dariomws @get-itips @tseward
Peer review needed for this PR. Thanks.

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

File
Status
Preview URL
Details

docset/windows/vpnclient/Set-VpnConnectionProxy.md
:white_check_mark:Succeeded

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 f052791:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/windows/vpnclient/Set-VpnConnectionProxy.md
:white_check_mark:Succeeded

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 5aff68d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/windows/vpnclient/Set-VpnConnectionProxy.md
:white_check_mark:Succeeded
View (win10-ps)

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


fix: improved handling of invalid Chart.yaml

This PR fixes handling of invalid Chart.yaml files - but still needs improvements in regard to rendering performance of the Helm panel when loading the helm/helm repo - see #2260
@devcatalin can you look into the performance - you can perhaps use this branch for improving?

Let's merge this as is, the performance will get fixed with the refactor of section blueprints for which I have a draft PR opened


CardField force focus when it's show up and it's blocking other user interactions.

Hello everybody!
Describe the bug
I have a form with several actions. It includes making a payment through stripe but when the user focuses on text input and after it scrolls the view and the card field shows up, the user can not do other interactions like press a button because automatically the focus goes to the CardField.
The situation is the same when the user is filling in the CardField, after it's filled the user cannot press some button because the focus again is for the CardField.
It's is very annoying, isn't it?.
is it a logical bug?
I tried to use autoFocus=false but it doesn't work. :(
Used in android, it is not tested yet in ios.

hey! I resolved it through this https://github.com/stripe/stripe-react-native/issues/429#issuecomment-881353718


🏃 Update go version to 1.13 for unit test docker image

Required when adding the webhooks feature
/cc @kashifest
/cc @fmuyassarov

/lgtm


expose listener count

Using this as a base to create libraries, it's very useful to know the listener count from time to time.

This can be done with relative ease on std platforms, but on no_std it's impossible to know how many listeners are in the last at any given time.

Sure, then a feature flag?

It sounds fine to restrict it to std only. I'll accept a PR

PR is online


Overload function report 'but implementation signatures of overloads are not externally visible.'

Bug Report
🔎  are not externally visible.
🕗 Version & Regression Information
typescript 4.2.0 and 4.3.0-dev20210228

I was unable to test this on prior versions,  and I reviewed the FAQ

⏯ Playground Link
https://www.typescriptlang.org/dev/bug-workbench/?https://www.typescriptlang.org/dev/bug-workbench/?#code/GYVwdgxgLglg9mABMOcAUMwAcRQFyIDkAjIQJQHEDcAUKJLAsqhtrgYQEzkGe33R4SFOkw58iAM5QATpgDmFRGBABbAEYBTGYgDeNRIcQzNUEDKQA5NVpmtxZGgF86LEuVfouHkWkIBmDyA
💻 Code

function foo(input: '1'): 1;
function foo(input: '2'): 2;
function foo(input: string): number {
    return Number(input)
}

foo('1')
foo('2')
foo('3')  <== not acceptable

🙁 Actual behavior
shows error:
No overload matches this call.
  Overload 1 of 2, '(input: "1"): 1', gave the following error.
    Argument of type '"3"' is not assignable to parameter of type '"1"'.
  Overload 2 of 2, '(input: "2"): 2', gave the following error.
    Argument of type '"3"' is not assignable to parameter of type '"2"'.(2769)
input.tsx(3, 10): The call would have succeeded against this implementation, but implementation signatures of overloads are not externally visible.
About
Docs
Asserts1
Export
Debug
Twoslash Overview
The bug workbench uses Twoslash to help you create accurate bug reports. Twoslash is a markup format for TypeScript files which lets you highlight code, handle-multiple files and show the files the TypeScript compiler creates.

The bug workbench lets make reproductions of bugs which are trivial to verify against many different versions of TypeScript over

🙂 Expected behavior
foo('3') should not throw error, and return type inferred as number

Working as intended.
https://www.typescriptlang.org/docs/handbook/functions.html#overloads

Note that the function pickCard(x): any piece is not part of the overload list, so it only has two overloads: one that takes an object and one that takes a number. Calling pickCard with any other parameter types would cause an error.

The function foo(input: string): number part of your implementation is not part of the signature overload list. If you want this you have to add another overload signature.

Thanks, see I just need to repeat function foo(input: string): number; twice


bindToWrapper: true not working in IOS

I set bindToWrapper: true but it seems to not work.
Not stop scrolling when I leave the current Wrapper
        var mainScroll = new IScroll('body > .main', {
            bounce: false,
            disableMouse: true,
            scrollbars: true,
            fadeScrollbars: true,
            disablePointer: true,
            bindToWrapper: true,
            preventDefaultException: { tagName: /.*/ }

It does the same for me - but I seems like a desirable behavior, as long as your keep your finger on the tablet (or your mouse button stays pressed).
=> Is this not a wrong documentation issue?


Shopify App Running on React/Express: Cannot read properties of undefined (reading 'from')

Hi, it would be great if somebody could take a look at an issue (a bug I suspect) I'm having. Appreciate any time spent.
Context:
I'm building a Shopify app (based on the Shopify Polaris framework) and haven't experienced this issue before. Throughout the development of the application, no errors of this type have been encountered. It seems very arbitrary and unlikely, but after small updates, this error started popping up and interfering with programming - I removed all changes I made that day to see if it would help, but it didn't. I've attached as much information as I find relevant below. Please let me know if it's not structured enough, not enough information, or too much information.
I'm running the latest version of express (see below for package.json)
{
  "name": "shopify-app-node",
  "private": true,
  "scripts": {
    "build": "npm run build:client",
    "build:client": "vite build --outDir dist/client",
    "debug": "node --inspect-brk server/index.js",
    "dev": "cross-env NODE_ENV=development nodemon server/index.js --watch ./server",
    "prepare": "husky install",
    "preserve": "npm run build",
    "serve": "cross-env NODE_ENV=production node server/index.js",
    "start": "npm run serve",
    "test": "vitest --reporter=verbose"
  },
  "type": "module",
  "engines": {
    "node": ">=16.13.0"
  },
  "dependencies": {
    "@apollo/client": "^3.5.10",
    "@shopify/app-bridge": "^2.0.22",
    "@shopify/app-bridge-react": "^2.0.24",
    "@shopify/app-bridge-utils": "^2.0.23",
    "@shopify/polaris": "^9.2.2",
    "@shopify/shopify-api": "^3.0.0",
    "@vitejs/plugin-react": "1.2.0",
    "compression": "^1.7.4",
    "cookie-parser": "^1.4.6",
    "cross-env": "^7.0.3",
    "dotenv": "^16.0.0",
    "express": "^4.17.3",
    "graphql": "^16.3.0",
    "react": "^17.0.2",
    "react-color": "^2.19.3",
    "react-dom": "^17.0.2",
    "react-grid-gallery": "^0.5.5",
    "react-qr-code": "^2.0.5",
    "serve-static": "^1.14.1",
    "vite": "^2.9.1"
  },
  "devDependencies": {
    "husky": "^7.0.4",
    "nodemon": "^2.0.15",
    "prettier": "^2.6.2",
    "pretty-quick": "^3.1.3",
    "supertest": "^6.2.2",
    "vitest": "^0.9.2"
  }
}

Trace from chrome devtools:
Uncaught TypeError: Cannot read properties of undefined (reading 'from')
    at node_modules/express/node_modules/safe-buffer/index.js (index.js:12:12)
    at __require2 (chunk-5537U2Q2.js?v=c1edecdf:47:50)
    at node_modules/express/lib/utils.js (utils.js:15:14)
    at __require2 (chunk-5537U2Q2.js?v=c1edecdf:47:50)
    at node_modules/express/lib/application.js (application.js:24:19)
    at __require2 (chunk-5537U2Q2.js?v=c1edecdf:47:50)
    at node_modules/express/lib/express.js (express.js:18:13)
    at __require2 (chunk-5537U2Q2.js?v=c1edecdf:47:50)
    at node_modules/express/index.js (index.js:11:18)
    at __require2 (chunk-5537U2Q2.js?v=c1edecdf:47:50)
node_modules/express/node_modules/safe-buffer/index.js @ index.js:12
__require2 @ chunk-5537U2Q2.js?v=c1edecdf:47
node_modules/express/lib/utils.js @ utils.js:15
__require2 @ chunk-5537U2Q2.js?v=c1edecdf:47
node_modules/express/lib/application.js @ application.js:24
__require2 @ chunk-5537U2Q2.js?v=c1edecdf:47
node_modules/express/lib/express.js @ express.js:18
__require2 @ chunk-5537U2Q2.js?v=c1edecdf:47
node_modules/express/index.js @ index.js:11
__require2 @ chunk-5537U2Q2.js?v=c1edecdf:47
(anonymous) @ dep:express:1

Here are the code lines highlighted in the trace:
if (Buffer.from && Buffer.alloc && Buffer.allocUnsafe && Buffer.allocUnsafeSlow) {
  module.exports = buffer

var Buffer = require('safe-buffer').Buffer

var compileETag = require('./utils').compileETag;

  return mod || (0, cb[__getOwnPropNames(cb)[0]])((mod = { exports: {} }).exports, mod), mod.exports;

module.exports = require('./lib/express');

Please let me know if there is any other information that might help out.
Thank you.

Hu @dev-segal sorry to hear about the troubles. I'm not sure what the issue is just with the information provided. Is it possible you can provide code we can run and the steps to reproduce the issue? We can then help debug and see what is causing it.

Hi Doug, my apologies. It seems my editor somehow added an import (without my knowing) and it lead to this error. It took a substantial amount of time (and embarrassing) but it seems like we should close this non existent bug :)
Thanks for your time,
Yehoshua

No problem, gald you got it resolved. Sorry for taking so long to get back to you in the first place!


This type appears in the class, not in the types.

Is there a thought to convert this lib to typescript?

Thanks. There are no plans to convert any of the PrismarineJS projects to typescript at this time. See some of the previous discussion on our Discord in the #contribute room about TypeScript.