[bulk] Validation: Absolute links

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

File
Status
Preview URL
Details

Skype/WebSDK/docs/troubleshooting/auth/AADAuth-EnableImplicitOAuth.md
:warning:Warning

Details

Skype/WebSDK/docs/troubleshooting/auth/AADAuth-IESecurityZones.md
:warning:Warning

Details

Skype/WebSDK/docs/troubleshooting/auth/AADAuth-EnableImplicitOAuth.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/WebSDK/docs/troubleshooting/auth/AADAuth-IESecurityZones.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

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 d42e34c:
:warning: Validation status: warnings

File
Status
Preview URL
Details

Skype/WebSDK/docs/troubleshooting/auth/AADAuth-AdminConsent.md
:warning:Warning

Details

Skype/WebSDK/docs/troubleshooting/auth/AADAuth-EnableImplicitOAuth.md
:warning:Warning

Details

Skype/WebSDK/docs/troubleshooting/auth/AADAuth-IESecurityZones.md
:warning:Warning

Details

Skype/UCMA/user-endpoints-and-application-endpoints.md
:bulb:Suggestion

Details

Skype/UCMA/user-impersonation.md
:bulb:Suggestion

Details

Skype/UCMA/using-an-audiovideoflow.md
:bulb:Suggestion

Details

Skype/WebSDK/docs/troubleshooting/auth/AADAuth-AdminConsent.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/WebSDK/docs/troubleshooting/auth/AADAuth-EnableImplicitOAuth.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/WebSDK/docs/troubleshooting/auth/AADAuth-IESecurityZones.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/UCMA/user-endpoints-and-application-endpoints.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.
Line 17, Column 5: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.applicationendpoint?view=ucma-api. Otherwise, remove the view parameter.
Line 19, Column 5: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.userendpoint?view=ucma-api. Otherwise, remove the view parameter.
Line 21, Column 67: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.localendpoint?view=ucma-api. Otherwise, remove the view parameter.
Line 29, Column 75: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.collaborationplatform?view=ucma-api. Otherwise, remove the view parameter.
Line 29, Column 242: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.applicationendpointsettings?view=ucma-api. Otherwise, remove the view parameter.
Line 29, Column 648: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.collaborationplatform.registerforapplicationendpointsettings?view=ucma-api. Otherwise, remove the view parameter.
Line 31, Column 480: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.applicationendpointsettings.useregistration?view=ucma-api. Otherwise, remove the view parameter.
Line 37, Column 274: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.topologyconfiguration.getapplicationtopologydata?view=ucma-api. Otherwise, remove the view parameter.
Line 37, Column 429: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.collaborationplatform.topologyconfiguration?view=ucma-api. Otherwise, remove the view parameter.
Line 37, Column 566: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.collaborationplatform?view=ucma-api. Otherwise, remove the view parameter.
Line 41, Column 139: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.applicationendpointsettings.isdefaultroutingendpoint?view=ucma-api. Otherwise, remove the view parameter.
Line 41, Column 298: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.applicationendpointsettings?view=ucma-api. Otherwise, remove the view parameter.
Line 45, Column 234: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.applicationendpoint.begindrain?view=ucma-api. Otherwise, remove the view parameter.
Line 45, Column 472: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.localendpointstate?view=ucma-api. Otherwise, remove the view parameter.
Line 45, Column 607: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.localendpoint.state?view=ucma-api. Otherwise, remove the view parameter.
Line 53, Column 1: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.userendpoint?view=ucma-api. Otherwise, remove the view parameter.
Line 55, Column 48: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.userendpointsettings?view=ucma-api. Otherwise, remove the view parameter.
Line 58, Column 147: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.signaling.sipendpoint.isendpointthrottled?view=ucma-api. Otherwise, remove the view parameter.
Line 69, Column 270: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.localendpointsettings.maxregisterretries?view=ucma-api. Otherwise, remove the view parameter.
Line 69, Column 401: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.localendpointsettings?view=ucma-api. Otherwise, remove the view parameter.
Line 69, Column 653: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.localendpointstate?view=ucma-api. Otherwise, remove the view parameter.
Line 71, Column 207: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.localendpoint.republishingrequired?view=ucma-api. Otherwise, remove the view parameter.
Line 75, Column 5: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.localendpoint.state?view=ucma-api. Otherwise, remove the view parameter.

Skype/UCMA/user-impersonation.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.
Line 15, Column 87: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.applicationendpoint?view=ucma-api. Otherwise, remove the view parameter.
Line 19, Column 157: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.userendpoint?view=ucma-api. Otherwise, remove the view parameter.

Skype/UCMA/using-an-audiovideoflow.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.
Line 15, Column 5: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.audiovideo.audiovideoflow?view=ucma-api. Otherwise, remove the view parameter.
Line 15, Column 104: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.audiovideo.audiocontrol?view=ucma-api. Otherwise, remove the view parameter.
Line 15, Column 203: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.audiovideo.audiochannel?view=ucma-api. Otherwise, remove the view parameter.
Line 17, Column 5: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.audiovideo.audiovideoflow.audio?view=ucma-api. Otherwise, remove the view parameter.
Line 17, Column 201: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.audiovideo.audiocontrol.getchannels?view=ucma-api. Otherwise, remove the view parameter.
Line 20, Column 107: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.audiovideo.audiochannel?view=ucma-api. Otherwise, remove the view parameter.
Line 26, Column 199: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.audiovideo.audiovideoflow.encryptionpolicy?view=ucma-api. Otherwise, remove the view parameter.
Line 26, Column 495: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.audiovideo.mediachannel.encrypted?view=ucma-api. Otherwise, remove the view parameter.
Line 28, Column 212: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.audiovideo.audiovideocall?view=ucma-api. Otherwise, remove the view parameter.
Line 28, Column 358: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.audiovideo.audiovideocall.flow?view=ucma-api. Otherwise, remove the view parameter.
Line 28, Column 599: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.audiovideo.audiovideoflowtemplate?view=ucma-api. Otherwise, remove the view parameter.

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 bdb63c9:
:warning: Validation status: warnings

File
Status
Preview URL
Details

Skype/WebSDK/docs/troubleshooting/auth/AADAuth-AdminConsent.md
:warning:Warning

Details

Skype/WebSDK/docs/troubleshooting/auth/AADAuth-EnableImplicitOAuth.md
:warning:Warning

Details

Skype/WebSDK/docs/troubleshooting/auth/AADAuth-IESecurityZones.md
:warning:Warning

Details

Skype/UCMA/user-endpoints-and-application-endpoints.md
:bulb:Suggestion

Details

Skype/UCMA/user-impersonation.md
:bulb:Suggestion

Details

Skype/UCMA/using-an-audiovideoflow.md
:bulb:Suggestion

Details

Skype/WebSDK/docs/troubleshooting/auth/AADAuth-AdminConsent.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/WebSDK/docs/troubleshooting/auth/AADAuth-EnableImplicitOAuth.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/WebSDK/docs/troubleshooting/auth/AADAuth-IESecurityZones.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/UCMA/user-endpoints-and-application-endpoints.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/UCMA/user-impersonation.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.
Line 15, Column 87: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.applicationendpoint?view=ucma-api. Otherwise, remove the view parameter.
Line 19, Column 157: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.userendpoint?view=ucma-api. Otherwise, remove the view parameter.

Skype/UCMA/using-an-audiovideoflow.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.
Line 15, Column 5: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.audiovideo.audiovideoflow?view=ucma-api. Otherwise, remove the view parameter.
Line 15, Column 104: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.audiovideo.audiocontrol?view=ucma-api. Otherwise, remove the view parameter.
Line 15, Column 203: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.audiovideo.audiochannel?view=ucma-api. Otherwise, remove the view parameter.
Line 17, Column 5: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.audiovideo.audiovideoflow.audio?view=ucma-api. Otherwise, remove the view parameter.
Line 17, Column 201: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.audiovideo.audiocontrol.getchannels?view=ucma-api. Otherwise, remove the view parameter.
Line 20, Column 107: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.audiovideo.audiochannel?view=ucma-api. Otherwise, remove the view parameter.
Line 26, Column 199: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.audiovideo.audiovideoflow.encryptionpolicy?view=ucma-api. Otherwise, remove the view parameter.
Line 26, Column 495: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.audiovideo.mediachannel.encrypted?view=ucma-api. Otherwise, remove the view parameter.
Line 28, Column 212: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.audiovideo.audiovideocall?view=ucma-api. Otherwise, remove the view parameter.
Line 28, Column 358: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.audiovideo.audiovideocall.flow?view=ucma-api. Otherwise, remove the view parameter.
Line 28, Column 599: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /dotnet/api/microsoft.rtc.collaboration.audiovideo.audiovideoflowtemplate?view=ucma-api. Otherwise, remove the view parameter.

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 2d31387:
:warning: Validation status: warnings

File
Status
Preview URL
Details

Skype/WebSDK/docs/troubleshooting/auth/AADAuth-AdminConsent.md
:warning:Warning

Details

Skype/WebSDK/docs/troubleshooting/auth/AADAuth-EnableImplicitOAuth.md
:warning:Warning

Details

Skype/WebSDK/docs/troubleshooting/auth/AADAuth-IESecurityZones.md
:warning:Warning

Details

Skype/UCMA/user-endpoints-and-application-endpoints.md
:bulb:Suggestion

Details

Skype/UCMA/user-impersonation.md
:white_check_mark:Succeeded

Skype/UCMA/using-an-audiovideoflow.md
:white_check_mark:Succeeded

Skype/WebSDK/docs/troubleshooting/auth/AADAuth-AdminConsent.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/WebSDK/docs/troubleshooting/auth/AADAuth-EnableImplicitOAuth.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/WebSDK/docs/troubleshooting/auth/AADAuth-IESecurityZones.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/UCMA/user-endpoints-and-application-endpoints.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

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 9e3dd23:
:warning: Validation status: warnings

File
Status
Preview URL
Details

Skype/WebSDK/docs/troubleshooting/auth/AADAuth-AdminConsent.md
:warning:Warning

Details

Skype/WebSDK/docs/troubleshooting/auth/AADAuth-EnableImplicitOAuth.md
:warning:Warning

Details

Skype/WebSDK/docs/troubleshooting/auth/AADAuth-IESecurityZones.md
:warning:Warning

Details

Skype/UCMA/user-endpoints-and-application-endpoints.md
:white_check_mark:Succeeded

Skype/UCMA/user-impersonation.md
:white_check_mark:Succeeded

Skype/UCMA/using-an-audiovideoflow.md
:white_check_mark:Succeeded

Skype/WebSDK/docs/troubleshooting/auth/AADAuth-AdminConsent.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/WebSDK/docs/troubleshooting/auth/AADAuth-EnableImplicitOAuth.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/WebSDK/docs/troubleshooting/auth/AADAuth-IESecurityZones.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

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 eed190f:
:warning: Validation status: warnings

File
Status
Preview URL
Details

Skype/WebSDK/docs/troubleshooting/auth/AADAuth-AdminConsent.md
:warning:Warning

Details

Skype/WebSDK/docs/troubleshooting/auth/AADAuth-EnableImplicitOAuth.md
:warning:Warning

Details

Skype/WebSDK/docs/troubleshooting/auth/AADAuth-IESecurityZones.md
:warning:Warning

Details

Skype/UCMA/user-endpoints-and-application-endpoints.md
:white_check_mark:Succeeded

Skype/UCMA/user-impersonation.md
:white_check_mark:Succeeded

Skype/UCMA/using-an-audiovideoflow.md
:white_check_mark:Succeeded

Skype/WebSDK/docs/troubleshooting/auth/AADAuth-AdminConsent.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/WebSDK/docs/troubleshooting/auth/AADAuth-EnableImplicitOAuth.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/WebSDK/docs/troubleshooting/auth/AADAuth-IESecurityZones.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

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

Global effort to fix build validation errors
@lindalu-MSFT
The Content & Learning team is fixing build validation errors on docs.microsoft.com for the rest of H2. This will eliminate potential accessibility, security, and usability issues. This PR includes only build validation fixes and does not change other content. Please review within five business days and merge or comment in the PR with any changes you’d like to see. Thank you!

@v-emilypr This is still in draft, do you want me to merge it anyway?

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

File
Status
Preview URL
Details

Skype/WebSDK/docs/troubleshooting/auth/AADAuth-AdminConsent.md
:warning:Warning

Details

Skype/WebSDK/docs/troubleshooting/auth/AADAuth-EnableImplicitOAuth.md
:warning:Warning

Details

Skype/WebSDK/docs/troubleshooting/auth/AADAuth-IESecurityZones.md
:warning:Warning

Details

Skype/UCMA/user-endpoints-and-application-endpoints.md
:white_check_mark:Succeeded

Skype/UCMA/user-impersonation.md
:white_check_mark:Succeeded

Skype/UCMA/using-an-audiovideoflow.md
:white_check_mark:Succeeded

Skype/WebSDK/docs/troubleshooting/auth/AADAuth-AdminConsent.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/WebSDK/docs/troubleshooting/auth/AADAuth-EnableImplicitOAuth.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/WebSDK/docs/troubleshooting/auth/AADAuth-IESecurityZones.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

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

@lindalu-MSFT, my apologies, I've moved this PR out of draft. Thank you!


Use raw Affine little-endian form of g1 encoded for PoP prove/verify

Fixed in: https://github.com/AntelopeIO/bls12-381/pull/11


Update free-courses-hi.md - add ethical hacking course hindi

What does this PR do?
Add resource(s) | This PR adds resources for Ethical Hacking courses in Hindi.
Remove resource(s) | Add info | Improve repo
For resources
Description
Ethical hacking is a growing field and very useful. The course provided starts from scratch and also provides a project experience.
Why is this valuable (or not)?
It is fully available on youtube for free.
How do we know it's really free?
For book lists, is it a book? For course lists, is it a course? etc.
It is a course
Checklist:

[ ] Read our contributing guidelines.
[ ] Search for duplicates.
[ ] Include author(s) and platform where appropriate.
[ ] Put lists in alphabetical order, correct spacing.
[ ] Add needed indications (PDF, access notes, under construction).
[ ] Used an informative name for this pull request.

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

Commited the changes, Please approve now!

Linter error is fixed. Please approve and merge!

Resolved the said changes and waiting for approval

Thanks, and welcome to free-programming-books!


update beam to use tRPC v10 syntax

This updates the tRPC syntax across the application to use the new tRPC v10 syntax. Benefits are:

Better Typescript: the compiler is faster in v10, so it's doing a better job.
Different naming conventions: uses the new, recommended naming convention from create-t3-app; specifically changing the trpc wrapper to be named api. Query/mutation hooks are now called as api.post.like.useMutation().
Easier maintainability: along with faster TS, it puts the application in line with the current version of tRPC.

I have not had the ability to test this in a live environment, so please hit me back with feedback/changes!

Created an additional commit upgrading prisma and @prisma/client to use the latest version, and updated the schema to reflect the updates. This solves this issue.


Allow calls to admin.hlx.page job details to work from log-viewer when requireAuth is not false

Related Issues
#810

Putting this on hold after a convo with @rofe and try and get log-viewer to use fetch for the data rather than send the user directly to the job details.
cc: @shsteimer

Fixed this in Log Viewer https://github.com/adobe/helix-tools-website/pull/37


Updated to work on 0.17.2

All entries of raw-wood -> wood to reflect changes in base.
All entries of stone-wall -> wall to reflect changes in base.
All sprites updated to the correct sprite named png file.
Coral06 sprite updated with correct sizes of 67x71.
Player inventory fundamentally changed, so old tags involving it are removed.
This should get you a headstart on 0.17 changes. Let me know if I messed something up.

Nice! Thanks for the contribution!

That's why you had the Image for the cross pipe at 0x0. Well that's not allowed to be done anymore, but 1x1 achieves the same effect.
I need to get you an actual canyon image to avoid such a bad hack that can get broken like this.

There is no canyon image to get, that's the point.
Not sure it's a "bad hack" when the official wiki documentation specifies 0 is the minimum. If anything this might be a bug in 0.17 -- unless I see a reference that this is a deliberate change perhaps it should be reported or else the wiki updated. Wube in the base mod uses 1x1 in many places but it's basically the same "bad hack" you now have.
The placeholder they use is "core/graphics/empty.png".
You can try swapping in that image if you prefer the self-documenting name, but be prepared to test because the actual png size of the picture have some automatic affects on collision boxes even for the same width and height values.

A bad hack that's been institutionalize is still a bad hack in my books. I'm a software engineer and computer scientist at my work, and I often am made to fix "solutions" like this. I mean the way it is currently, it appears that the maze canyon is "black water."
If you don't mind, I just want to replace that with something that actually looks like a canyon, possibly with 9 unique images that make it look continuous.

Erm, I have the same day job, it's meaningless to pull that out in a discussion because imagine if a colleague does something that could be improved, do you point out that you are a professional as a way to win an argument -- no because they are too.
Anyway. You the actual discussion.
I think you are missing an aspect -- the tiles are the chasm artwork, not the maze target. By all means improve the tile artwork, that's where you will have the flexibility to do so because tiles support transitions with other tiles. Which is why I went with water, so I got some three-dimensionality where it meets land.
I am a bad artist for sure.
The real bad hack is that I have to have a picture, or perhaps that I have to have two entities at all to get all the behaviours I need. But these are limitations of the API. Raise it with Wube. Improve tile artwork only in the meantime.
The targets have no artwork.

Please note that improved tiles would need to go in a separate PR, this PR should be to get 0.17 working as-is

Listen, I didn't mean to offend you. I'm just calling it out as I see it, and I understand that it's the example the devs put out, but it isn't how it should have to be.
I also wasn't suggesting we do that for 0.17 right away anyways. I already have a server going with my changes, and I'll report and/or fix any problems I encounter over the course of the weekend. So far though, the only thing I've see is if water is at a dead end that dead ends in the north direction, the water tiles glitch into the canyon for some reason.

I'm not offended, it just isn't a hack we can solve. I need a tile and I need a target. I don't want the tile artwork covered by other artwork. That was my only point

I've added a separate issue for the problem you mentioned with water at dead ends

I'm running this branch on a lightly-modded local 0.17 world (mostly because i want to play it, but 0.17), and it seems to be functional.
Only note - having a weird glitch on the sides of water - cant walk on them, but still, odd looking (using 64 chunk size) https://www.dropbox.com/s/amk0vflo29t0ltd/RibbonMazeWeirdness.png?dl=0

Looks like tile transitions have changed. If I remember correctly, it looked like this in an early version of the mod, when I had a different layer value for maze chasm than for water. So probably it's a layer change in the water prototype, or something related to it.

On consideration, I don't think I'll raise the issue of having no image on the forums.
I actually think it's not even a hack at all, rather the opposite. It's an invariant that all entities have a picture, so an empty image is the correct solution.

I downloaded this fork to play with it on a server with friends, and i'm encountering and interesting issue, which is that connecting with the mod active is no issue, but if I connect to a save generated with it, i consistently immediately get desyncs.
The only other mods I have active are bottleneck, EvoGUI and Todo List.

nbieck: Was this on 0.17.7? There is an issue with that release and mods. Update instead to 0.17.8.  Other than that, explain what you mean about desyncs? It was my understanding that a desync can't happen unless a person's computer isn't able to keep up with the game speed on the server.

This is has been occurring with both 0.17.8 and 0.17.9 which just released. I'm also planning to look into this further, but i have attached the latest desync report that was generated for reference.
desync-report-2019-03-08_21-17-03.zip

Desyncs can happen if the game state is modified non-deterministically. So for example with random numbers all players need to share the same seed and use a deterministic and platform independent RNG.
 If it's still happening that would likely indicate a bug in the core game and could be raised on the forums.

Desyncs can happen if the game state is modified non-deterministically.

Just as a note, one of the biggest causes of desyncs-at-savegame-load-time (but not on initial game creation) by mods is event handlers being dynamically registered based on conditioned.  It needs to match all players as how the game loads except in certain very careful cases.  I.E. if a handler is registered at any time then it should be registered from the very beginning and always (just be a no-op if nothing it needs to do).  Of course minimizing handlers is good overall.

True, I don't have any conditional event handlers for that reason. Also no conditional requires.
Relevant file here: https://github.com/h8ul-modder/factorio-ribbon-maze/blob/master/control.lua
Seems anyway this is happening only when mod is disabled

I tested loading the map without any mods enabled, and that did not result in a desync.


Configure automatically generated release notes

Problem:
To have GitHub automatically generate release notes, we'll need to create some configuration and labels
Solution:
See https://docs.github.com/en/repositories/releasing-projects-on-github/automatically-generated-release-notes#configuring-automatically-generated-release-notes for steps

We updated the release scripts to set generate_release_notes=true when calling https://docs.github.com/en/rest/releases/releases?apiVersion=2022-11-28#create-a-release after about v1.9.2


Fuubar not compatible with Rspec 3.8

Current Problem
Fuubar has an rspec dependency of "~> 3.7"
I recently tried to update rspec in my project to 3.8, and i could not do it without removing the fuubar gem.
I like the fuubar gem, so I would like to see it support rspec 3.8.
Potential Solution
Remove rspec 3.7 restriction
Mockups
# in fuubar.gemspec
spec.add_development_dependency 'rspec',            ["~> 3.8"]

@ethan-dowler that's only for a development dependency, which doesn't affect users of the gem.  Even still both that dependency and the rspec-core dependency is pessimistic.  Which means it'll work until RSpec 4.0.
Something else must be going on in your Gemfile.

Odds are you didn't properly bundle update which told you there was a conflict when there really wasn't.  It's a common issue.

ha. probably. one of my other apps updated fine. I'll double check everything. Thanks.


Slug generation not functioning correctly Wagtail 5.0

Slug generation doesn't appear to functioning correctly on pages inheriting 'MetadataPageMixin'
e.g. Page title: 'My New Home Page', Slug: 'My New Home Page' rather than 'my-new-home-page'

yeah I came across this in another project, looks like wagtail moved the functionality to a widget
This line: https://github.com/neon-jungle/wagtail-metadata/blob/master/wagtailmetadata/models.py#L94C13-L94C32
Needs to be updated to follow these instructions - https://docs.wagtail.org/en/stable/releases/5.0.html#slug-field-auto-cleaning-now-relies-on-data-attributes

yeah I came across this in another project, looks like wagtail moved the functionality to a widget This line: https://github.com/neon-jungle/wagtail-metadata/blob/master/wagtailmetadata/models.py#L94C13-L94C32
Needs to be updated to follow these instructions - https://docs.wagtail.org/en/stable/releases/5.0.html#slug-field-auto-cleaning-now-relies-on-data-attributes

Thank you, I don't think I would have found that.
I changed the promote_panels to
 promote_panels = [
        MultiFieldPanel([
            FieldPanel("slug", widget=SlugInput),
            FieldPanel('seo_title'),
            FieldPanel('show_in_menus'),
            FieldPanel('search_description'),
            FieldPanel('search_image'),
        ], gettext_lazy('Common page configuration')),
    ]

and added

from wagtail.admin.widgets.slug import SlugInput

I had a similar problem and this solution works.


Can't add a password to the default user if I didnt set one during install

Describe the bug
I installed bazzite on a usb and didnt add a password to the user when I was installing the OS. After using the OS I decided to keep using it but now I cant add a password to my default user.
What did you expect to happen?
When I go to the settings -> User section the settings are greyed out:

Output of rpm-ostree status
State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-gnome-nvidia:stable
                   Digest: sha256:81850d0fb4899bfd721ac60ac37e1e4f1c2f5154190dc6bb957f8ae411378aaf
                  Version: 39.20240116.0 (2024-03-22T17:15:49Z)
          LayeredPackages: micro sunshine
                Initramfs: '"-I /etc/crypttab /usr/lib/modprobe.d/nvidia.conf" '

  ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-gnome-nvidia:stable
                   Digest: sha256:178c01cc01532f0daf132806f1c6e67a01c81f518a3f9baf59d5605dd00f5e21
                  Version: 39.20240116.0 (2024-03-15T23:46:23Z)
                Initramfs: '"-I /etc/crypttab /usr/lib/modprobe.d/nvidia.conf" '

Hardware
No response
Extra information or context
No response

this is caused by the installer even letting you set a blank password to begin with, which we do not have control over sadly.
Try opening terminal and type passwd to change it, keep in mind no characters will show up when you type in the password so make sure you type it in correctly.
if that does not work then you will have to re-install and follow the installation guide


When editing your channel, clicking a subscribed channel results in a display error.

Bug
When you are editing your channel and click a channel that you are subscribed to (on the right-hand side), it will result in some wonky behaviour, displaying whatever channel you clicked on instead of yours at the top.
To Reproduce
Steps to reproduce the behavior:

Go to a channel that you have claimed
Click on the edit button
Click on a channel you are subscribed to.
See error

Expected behavior
This should prompt you to either save your changes or discard them, OR just simply take you to the channel that you clicked.
Screenshots
GIF Showing the Bug: https://i.imgur.com/aV04lG5.gif
System Configuration

LBRY Daemon version: 0.46.1
LBRY App version: 0.37.2
LBRY Installation ID: 2TxtRu7JxCpVxNF572y4tir3kiiH3ni5djXhQo9CTzY2V7vAPB94cEd3cBeSaaKDJu
Operating system: Windows 10

Can confirm this does occur on my EndeavourOS Linux install (Arch derivative), kernel 5.3.12-arch1-1.

Thank you for the solid bug report. Should be simple to fix.


add local DB

add a local DB so that it doesn't have to depended on us

this might get merged into the asignment feature

UPDATE I'm thinking of using a frontend databse instead of local storage. Reminder for me: make sure to reasearch on what frontend database is useful for this apllication.


feat(pointcloud): Update the backgroundColor of pointCloud

:tada: This PR is included in version 1.0.0 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:


npm install -d failed on my system

npm ERR! owner ls Couldn't get owner data nw-tests
npm ERR! 404 404 Not Found: nw-tests
npm ERR! 404
npm ERR! 404 'nw-tests' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, or http url, or git url.

npm ERR! System Darwin 14.3.0
npm ERR! command "/Users/None/Develop/node-v0.10.32-darwin-x64/bin/node" "/Users/None/Develop/node-v0.10.32-darwin-x64/bin/npm" "owner" "ls" "nw-tests"
npm ERR! cwd /Users/None/node-webkit/nw.js/tests
npm ERR! node -v v0.10.32
npm ERR! npm -v 1.4.28
npm ERR! code E404
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /Users/None/node-webkit/nw.js/tests/npm-debug.log
npm ERR! not ok code 0

What application you trying to run?

tests under nw.js
sorry, maybe I should open the issue in webkit repos ...

I think so.
I checked and don't understand why it try to download nw-tests when you run npm install -d inside folder of nw-tests package...
You may want to ask here https://gitter.im/nwjs/nw.js, can get faster answer

ok, thank you.


Add option for fixed size of the calendar

Lets to set fixed size of the calendar (6 rows of weeks). In addition, lets to prevent issue with top position of the calendar.
Without fixed size:

Fixed size:

[Current coverage][cc-pull] is 93.63%

Merging [#519][cc-pull] into [master][cc-base-branch] will decrease coverage by 0.28%

@@             master       #519   diff @@
==========================================
  Files            10         10
  Lines           329        330     +1
  Methods          13         13
  Messages          0          0
  Branches         48         49     +1
==========================================
  Hits            309        309
  Misses           14         14
- Partials          6          7     +1

[][cc-pull]

Powered by Codecov. Last updated by [8da6d8a...6c98f9d][cc-compare]
[cc-base-branch]: https://codecov.io/gh/Hacker0x01/react-datepicker/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/Hacker0x01/react-datepicker/compare/8da6d8a6f2964fce814a19d594648c25f1e6c44e...6c98f9d31c703a4b0a208a6f840bf4342cd013fc
[cc-pull]: https://codecov.io/gh/Hacker0x01/react-datepicker/pull/519?src=pr

Can we call this flag fixedHeight instead?

@rafeememon Yes, sure.

@rafeememon Done

LGTM 👍

@alextkachuk thanks for the PR!
Re #361, #510

thanks for this fix!


simplify netCDF download

Some more small simplifications after #42. I tested locally and the link does not seem to need the download attribute.

Nice I tried it too and seems to work perfectly, thanks!

Thanks


IdP metadata parser/merger adjustments

This tackles the following issues:

https://github.com/onelogin/python3-saml/issues/17
https://github.com/onelogin/python3-saml/issues/18
https://github.com/onelogin/python3-saml/issues/19
https://github.com/onelogin/python3-saml/issues/20

@pitbulk I hope these are good for you :-) While I needed to touch the tests quite a lot, this new behavior should still be backwards-compatible.

Thanks for your quick feedback @pitbulk, really appreciate. I have left comments/questions!

Thanks for feedback, once again. Updated the branch, please review again, thanks!


[Feature]: Treat pyptoject.toml as one of the default config files if toml support is present

To Dos

[X] I have checked the issues and think that this is not a duplicate.

[X] I added a very descriptive title to this issue.

Description
If toml support is present (tomli intalled or python 3.11) in cases where directory is passed search for .rstcheck.cfg | setup.cfg AND pyproject.toml instead of only .rstcheck.cfg | setup.cfg
Operating System
Linux
Operating System Details
No response
Python Version
3.11.4
rstcheck Version
6.1.2

I can partially confirm the issue. If tomli is installed the toml support is active. Python >= 3.11 does not trigger toml support.


Add Notifications API

The Notifications API will be used to notify a SOC User that a Threat was received with a particular Threat Level.  The following components will need to be changed:
Metron Threat Intel Configs:

parser/enrichment/triage_configs

Please use the issue # to commit any changes.  This will allow us to track the commits related to this Issue

The Notification endpoint has been added to master trunk, but it doesn't send an email ( /api/notification/email).  Please download our master, find the issue and fix it.
In regards to SMS, the /api/notification/sms I don't see any parameters being parsed.  We should be parsing SMS phone number and Message, which should contain a link to login to review the threat.
The above endpoints are great for having a generic way to send notifications.  But, when sending this from Metron we should just be POSTing the Company, Site, Score to the /api/notification API and you should figure out who should be notified based on the users notification settings.

Here's more detail on how we should be handling alerts coming from metron using the /api/metron/alerts URL.
We just need the threat id, company id, site id and score so that we can figure out who needs to be notified.  So, above class needs to be changed so that it looks up the user that should be notified and notify that user.  So, I would like to see a test where we send
/api/metron/alerts this payload
{
“threat_id": "ASnFODKFNDSK-23DSJO”,
“company_id” : “Flyball-Labs”,
“site_id” : “Site 1”,
“score” : 15
}
Then we should fire off a notification to users that are attached to the company id and/or site.  The notification should either be an Email or SMS based on their notification preferences.

Per our conversation, we agreed to change the payload to being the complete threat intel message.  So, the /api/metron/alerts payload will just contain
{
"message":
}


stellar smart contract

closes #8

@ElliotFriend  please look through this draft PR

closes #8

@ElliotFriend please look through this PR

@Ugo-X Thanks for pointing out that error! Looks like this is my fault (from b136432f828559a4e0ce25950156ed8048f6cec3), when I was trying to fix a build failure.  Looks like this is my fault (from b136432), when I was trying to fix a build failure. Lemme get this worked out and I'll let you know how it comes along

alright, thanks chief, will be waiting for a response.

@Ugo-X I think I got this worked out. removed an old rollup configuration, and now we "should" be all set for both build/dev environments. Give it another shot, and let me know how it gets on.

@ElliotFriend please review again ser

🫠


single thumbnail in top of range select

we should test with real thumbnail i can't right now because i don't have video with thumbnail


swap out FilterableTable.jsx for @data-ui/data-table

swap out javascripts/components/FilterableTable/FilterableTable.jsx for data-ui/data-table

This would be great -- the FilterableTable component chokes quite badly with larger sets of data.

Notice: this issue has been closed because it has been inactive for 305 days. Feel free to comment and request for this issue to be reopened.


Set top level token permissions

With the re-worked workflows I close this PR and open a new if required.


feat(execution): add l2_gas_price to FeeEstimation

This change is

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#644  👈
#643
#641
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @TzahiTaub and the rest of your teammates on  Graphite


Update the mod to be compatible with Factorio 0.17

This updates the mod to work with Factorio 0.17.
For non-developers reading this and just wanting a working version: Throw https://www.poempelfox.de/tmp/AtomicArtillery_0.1.6.zip into your factorio-mods-directory (but don't forget to delete it once the proper update reaches mods.factorio.com).

Thanks a lot, I've been meaning to get around to this but I've been slacking a lot on updating my now old projects, including this one.


URL for Thermal is hardcoded

The URL for Thermal in Chassis (l38 in /src/system_operations.go) is hardcoded. The collection should be retrieved from PSME and the url should be set based on the response.

@ehaligow Thanks for sharing this. We already knew all like issues. All kinds of the same issue will fix in the next version.


Doesn't work with latest version of amqp-client.jar

When I have version 3.4.4 of the amqp-client.jar installed, it works.  When I upgrade to 3.5.x, it throws an error because "AMQP.BasicProperties::setHeaders" method was removed.
https://www.rabbitmq.com/releases/rabbitmq-java-client/v3.5.0/rabbitmq-java-client-javadoc-3.5.0/com/rabbitmq/client/AMQP.BasicProperties.html

Thanks for the heads up.  A pull request would be most welcome :)

Sure, PR available here: https://github.com/jlavallee/JMeter-Rabbit-AMQP/pull/23


Transcoding audio to PCM, processing and writing back to another video: possible ?

Hi,
I'm trying to postprocess audio from any  video source.
To do so, I intend to:

convert source audio frames (whatever codec), to raw PCM S16LE stereo.
postprocess my raw S16LE data
encode the postprocesed  S16LE data to back Audio Frames as "wav" codec, in another video

Is that somehow possible with PyAV?
Thanks in advance!

The stumbling block at this point might be copying video data without transcoding it. I don't recall the status of that sort of thing... maybe it works for simple video.


Do not look for spaces when checking for invalid characters

Details

This is just a quick follow up to an issue found in this PR https://github.com/Expensify/App/pull/13693
Fixed Issues

Follow up to https://github.com/Expensify/App/pull/13693
Tests

Go to Settings->Profile->Display Name
Change your name and include a comma ,
Try to Save
Verify that it gives you an error
Remove the comma and change your name to include a semicolon ;
Try to Save
Verify that it gives you an error
Remove the semicolon and change your name to include a plus sign+
Try to Save
Verify that it changed by refreshing
Remove the + and save your name to something different
Verify that it changed by refreshing
Add a space to you name by including a middle name in the first name input field
Save the name and verify it got saved with the space just fine

[x] Verify that no errors appear in the JS console

Offline tests

Same as online.
QA Steps

[ ] Verify that no errors appear in the JS console

Same as tests
PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is correct English and approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

Mobile Web - Chrome

Mobile Web - Safari

Desktop

iOS

Android

Reviewer Checklist

[ ] I have verified the author checklist is complete (all boxes are checked off).
[ ] I verified the correct issue is linked in the ### Fixed Issues section above
[ ] I verified testing steps are clear and they cover the changes made in this PR

[ ] I verified the steps for local testing are in the Tests section
[ ] I verified the steps for Staging and/or Production testing are in the QA steps section
[ ] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[ ] I checked that screenshots or videos are included for tests on all platforms
[ ] I included screenshots or videos for tests on all platforms
[ ] I verified tests pass on all platforms & I tested again on:

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[ ] MacOS / Chrome / Safari
[ ] MacOS / Desktop

[ ] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[ ] I verified proper code patterns were followed (see Reviewing the code)

[ ] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[ ] I verified that comments were added to code that is not self explanatory
[ ] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[ ] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[ ] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[ ] I verified any copy / text that was added to the app is correct English and approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[ ] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I verified that this PR follows the guidelines as stated in the Review Guidelines
[ ] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[ ] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[ ] All JSX used for rendering exists in the render method
[ ] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[ ] If any new file was added I verified that:

[ ] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[ ] If a new CSS style is added I verified that:

[ ] A similar style doesn't already exist
[ ] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[ ] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[ ] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[ ] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

Mobile Web - Chrome

Mobile Web - Safari

Desktop

iOS

Android

Quick question though if we enter both ; & , we are always showing the remove comma alone, instead remove both or all invalid characters, are we fine with this?

I think that is fine, you will need to remove it and then just remove semicolon.
This is more an edge case after all, who has comma or semicolon in their name?

Thank you @luacmartins and Santosh

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by @mountiny in version: 1.2.44-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by @chiragsalian in version: 1.2.44-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Fix for the join_axes on concat method

join-axes on .concat() is not working any more.
I took the solution from this post.
Hope it helps.
https://github.com/pandas-dev/pandas/issues/21951
only works with list-like join_axes
# pd.concat([one, two], join='outer', axis=1, join_axes=[two.index])
# #      a    b   b   c
# # 1  2.0  3.0  10  11
# # 2  NaN  NaN  12  13

# ## cleaner with reindex?
# pd.concat([one, two], join='outer', axis=1).reindex(two.index)
# #      a    b     b     c

Coverage remained the same at 0.0% when pulling 4a5f96f1ca9098e5ba251d6ddd1438d5dfa1b984 on martineserios:pandas-concat-fix into 9d4ce879029335b7044e1b3d84bb2765b8950457 on timcera:master.

Coverage remained the same at 0.0% when pulling 4a5f96f1ca9098e5ba251d6ddd1438d5dfa1b984 on martineserios:pandas-concat-fix into 9d4ce879029335b7044e1b3d84bb2765b8950457 on timcera:master.

Actually, since this is a one-line change it doesn't make sense to go through all of the git rigmarole.  I will go ahead and make the edit, and close this pull request.
Thanks!


Create RM-Subscription Count Cluster query

This will not be ready for R1

There are still questions to address for the Subscription Count query, so this will be targeted for release 1.2

The subscription count query is complete and has been added to the repository at
https://github.com/folio-org/folio-analytics/tree/main/sql/report_queries/subscriptions


no 'rtsol' anymore for OpenBSD -current

Hi,
just figured, that the 'rtsol' paramter on OpenBSD -current is 'gone'.
Now it's 'inet6 autoconf' to enable the same functionality.
Sebastian

Thank you.

Does that mean 5.7 will ship with this change?

Yes, the current 5.7 beta doesn't have the rtsol daemon anymore. This functionality now moved to the kernel.
Have a patch already prepared, when the other one is merged, I go create a new branch with that one.

5.7 has been released.  I'm slow to upgrade.  Hopefully in the next week or so.

I also hope, to find a bit time next week. The question basically is:
do you want to stay backward compatible or not?
I guess yes, ;)
So with backward compatibiliy, should the user disinguish between pre and after 5.6, and give the right options, i.e. rtsol for 5.6, and 'inet autoconf' for 5.7 and onward.
OR should the module smart enough, if either of both is given, based on the OS version, it will figure it out automatically?
For the sake of easier implementation I'd go for the first one, so the admin has to specify the right parameters for the OS version he is using/managing.
What do you think?

I'm thinking about from the perspective where a user doesn't read the release notes.  The module poses the question "would you like to accept router advertisements", and I'd think it would make for a better user experience to just be able to answer "yes" without having to understand what the underlying options are.  I only really care about being backwards compatible for a version or so.  Given that OpenBSD really only seems to support the latest version, lets just move with that, but assist in the transition.
Code wins arguments though, so if you get at thing working, then lets review it.  We could go with the first option you mentioned, but lets document it somewhere, so people coming in new or upgrading know what they are getting into.

@buzzdeee Did we get this resolved?  Now that 5.8 is on its way, I care even less about old versions.

@xaque208 jepp, that was PR #57 , and this was forgot to be closed.


[RFC] display hints (:x, :b, :a)

this is a feature proposed for version 0.2.0.
(this feature cannot be implemented in the 0.1.x series because it involves breaking changes in the wire format, parser and/or decoder.)
the design is not final and it's still being reviewed by the knurling team.
1. optional type annotation
(0.2's {} === 0.1's {:?})
In v0.2.0, the empty format parameter ({}) will be accepted. It will be understood as 'this is some impl Format value'.
// 0.1.x
info!("{:?}", 42);

// 0.2.x -- equivalent
info!("{}", 42);

it will still possible to specify the type to improve encoding size
info!("{:u8}", 42);

this feature combined with feature (3) will ease migration from the log! macro to the defmt macros
2. default to Display-like format (fallback to Debug)
in 0.2.0 types, like strings, will be formatted "Display-like", that is without double quotes and escaped characters
// 0.2.x
info!("{}", "hello\tworld");
// -> INFO hello    world

// 0.1.x
info!("{}", "hello\tworld");
// -> INFO "hello\tworld"

if a type has no Display-like formatting option, it will formatted in a Debug-like fashion
info!("{}", [0, 1]);
// -> INFO [0, 1]

0.1.x defaulted to the Debug-like format
3. display hints
syntax
"display hints" can be tacked onto format parameters to tell a defmt printer that you want a value to be formatted (on the host side) in a certain way
as this is a hint, a printer (the host) may choose to ignore the hint
// `Format` value
info!("{:x}",    42); // -> INFO 0x2a

// typed value
info!("{:u8:x}", 42); // -> INFO 0x2a

the hint propagates inwards and applies to struct / enum fields (recursively)
struct S { x: u8, y: u8 }

info!("{:x}", S { x: 32, y: 33 });
// -> INFO S { x: 0x20, y: 0x21 }

initial support
initially we plan to support the following hints:

x (lowercase), X (uppercase) hexadecimal
b binary
a ASCII

the ASCII hint applies to byte arrays and slices.
when the printer sees this hint it should format the bytes using Rust's byte string literal notation.
Example:
info!("{:a}", [104, 105, 127]);
// -> INFO b"hi\x7f"

forward compatibility
to allow for the possibility of adding more display hints in the v0.2.x series, defmt tools should ignore display hints they don't understand instead of throwing errors.
info!("{:x}",   42); // -> INFO 0x2a
// hint not understood
info!("{:04x}", 42); // -> INFO 42

impl notes
// existing enum in `decoder` that was renamed
enum ArgKind {
   Uxx(u64),
   // ..
}

// replaces the 0.1.x `enum Arg`
struct Arg {
    kind: ArgKind,
    hint: Hint,
}

#[non_exhaustive] // for forwards compatibility
enum Hint {
    Hexadecimal { uppercase: bool },
    Binary,
    Ascii,
    Unknown(String), // not understood in this version
}

unresolved questions

pick default hexadecimal display format: 0x1234_5678 (with 0x suffix and grouping)?
pick default binary display format: 0b1111_0000 (with 0b suffix and grouping)?
how to switch to Debug-like format (e.g. for strings)? :? or :#?

this feature cannot be implemented in the 0.1.x series because it involves breaking changes in the wire format, parser and/or decoder.

to expand on this: existing probe-run versions like 0.1.6 expect a certain format string syntax. if we extend the format string syntax in defmt 0.1.x then probe-run 0.1.6 will fail to decode the defmt data. The failure mode is silent failure: the log stream stops and the application keeps running.
for that reason any change in the format string syntax needs to be done in defmt 0.2.0. That defmt version will work with a probe-run 0.2.0, which will not work with defmt 0.1.0: the tool will reject apps that use defmt 0.1 -- it will refuse to flash them and tell you to use a different probe-run version

initial support

note that the goal of this RFC is not to list upfront all the possible display hints but rather specify the feature in a way that let us add new display hints without those additions being breaking changes. That way we can add display hints in the 0.2.x series

syntax

The prosposed syntax feels somewhat ambiguous...?

If I have {:foo}, is foo supposed to be a type or a hint? There's no way to know other than checking foo against a list of known types/hints.
What orders are allowed? {:hint:type} or {:type:hint}, or both?

Alternative 1: join both into string, and require the hints to be "prefixes" to the type.
info!("{}", 42);
info!("{:u8}", 42);
info!("{:x}", 42);
info!("{:xu8}", 42);

good: more terse, faster to type
bad: harder to parse unknown hints for forwards-compat
bad: {:istr} is istr, or str with format hint i? :(

Alternative 2: specify type with one special char, hint with another. For example using : for hints, = for types:
info!("{}", 42);
info!("{=u8}", 42);
info!("{:x}", 42);
info!("{:x=u8}", 42);
info!("{=u8:x}", 42);

good: separates the concept of "type" and the concept of "format hint" very clearly
good: easy to parse unknown hints
bad: very incompatible

: for types, = for hints -> very incompatible with std fmt
: for hints, = for types -> very incompatible with defmt 1.x.
if I had to choose, I'd prioritize std fmt compatibility, because:

long term more people will be migrating to defmt 2 from std than from defmt 1
having special different syntax for the concept of "type" makes it clear that it's a very different concept, makes defmt easier to learn IMO.

to allow for the possibility of adding more display hints in the v0.2.x series, defmt tools should ignore display hints they don't understand instead of throwing errors.

Just to clarify, this means the decoder ignores unknown hints, but the  macros still reject unknown hints?

pick default display format

:+1: to the prefix: removes ambiguity and makes pasting to other tools do the right thing.
:-1: to the grouping: it'll be annoying if you want to paste values to some calculator/language that doesn't support them.

how to switch to Debug-like format (e.g. for strings)?

I'd say format hint ?, to be consistent with std.
How does it interact with structs? my guess is like this:
struct S { x: &str }

info!("{}", S { x: "hello!" });
// -> INFO S { x: hello! }
info!("{:?}", S { x: "hello!" });
// -> INFO S { x: "hello!" }

the ASCII hint applies to byte arrays and slices.
Printing quoted strings is also useful for str though. This somewhat overlaps with ?, but it feels weird to me that if you want a quoted string from a [u8] you need to use a and from a str you need to use ?

The prosposed syntax feels somewhat ambiguous...?

we'll like to ease migration from log and have some level of inter-op between defmt and log so I think we'd like to use :hint syntax (with the leading semicolon). That way the format specifier {:x} works both with defmt and log.
the syntax for the type is not set in stone. prefixing it with a different symbol, e.g. =u8 seems reasonable.
as a side note we also considered moving the type info to the arguments, e.g. using type ascription syntax:
// alternative
info!("{:x}", x: u8);
// this proposal
info!("{:u8:x}", x);

but this is incompatible with the "bitfield range" type: {:4..8}

Just to clarify, this means
the decoder ignores unknown hints,

yes

but the macros still reject unknown hints?

this is unspecified. as far as forward compatibility is concerned I think it should be possible to have macros reject unknown hints at compile time. the main compatibility problem is: using a newer defmt patch version with an old probe-run (that supports the defmt major.minor version). as long as the probe-run's parser ignores unknown hints we should be fine; it should be OK if the macros' parser errors on unknown hints.

How does it interact with structs?

good question

// -> INFO S { x: hello! }

this looks odd to me because in my mind S { .. } is already Debug-like format so inner fields shouldn't use Display-like format.
I would vote for structs / enums are always (recursively) Debug-like and the :? hint has no effect on them

it should be OK if the macros' parser errors on unknown hints.

Yeah, IMO it's the best thing. Macros shouldn't silently ignore errors, otherwise you can typo your format hint and waste time trying to figure out why is it doing nothing.

this looks odd to me because in my mind S { .. } is already Debug-like format so inner fields shouldn't use Display-like format.
I would vote for structs / enums are always (recursively) Debug-like and the :? hint has no effect on them

Yeah this looks odd to me too, but it's what current defmt does. It makes sense to print all structs quoted (the generated Format impl could just put {:?} everywhere)

I have incorporated the feedback into the RFC (issue description)

the hint propagates inwards and applies to struct / enum fields (recursively)

we need to specify what's the behavior of "hint collision":
struct S { x: u8 }
impl Format for S {
    fn format(&self, f: &mut Formatter) {
        write!(f, "{:b}", self.x);
    }
}
// does this use hexadecimal notation or binary notation?
info!("{:x}", S { x: 16 });

the core::fmt behavior is to ignore the outer format specifier:
impl fmt::Debug for S {
    fn fmt(&self, f: &mut fmt::Formatter) -> fmt::Result {
        write!(f, "S {{ x: {:b} }}", self.x)
        //                   ^ cannot be overriden
    }
}
// the `x` specifier is ignored
println!("{:x?}", S { x: 16 }); // -> S { x: 1000 }

Using the innermost specifier sounds like a reasonable thing to do

implemented in #313


Build up Executor based on version 6.2.3 Rest/HighRest Client

[]  Raw Json High Rest Client - IElasticRawHighExecutor & ElasticRawHighExecutor
[]  Raw Json Rest Client
[]  Clz Based High Rest Client
[]  Clz Based High Rest Client

However, it is not easy and clear to handle with the Aggregation :
public interface Aggregation extends ToXContentFragment {

    /**
     * Delimiter used when prefixing aggregation names with their type
     * using the typed_keys parameter
     */
    String TYPED_KEYS_DELIMITER = "#";

    /**
     * @return The name of this aggregation.
     */
    String getName();

    /**
     * @return a string representing the type of the aggregation. This type is added to
     * the aggregation name in the response, so that it can later be used by clients
     * to determine type of the aggregation and parse it into the proper object.
     */
    String getType();

    /**
     * Get the optional byte array metadata that was set on the aggregation
     */
    Map<String, Object> getMetaData();

...
}

Aggregation itself does not provide any use method beside type information (mostly is because too complicated aggregation result data format it could return).
You may need to switch each Aggregation's type (String) to find out which one is which one even with help of AggreationBuilder provided.


[Feature] Emit OnSessionHang automatically on subscription liveliness timeout

Feature description
When we MarkAsDefunct for outbound messages, we also dispatch OnSessionHang:
https://github.com/project-chip/connectedhomeip/blob/a6ecd62777cd2d9646f13d809b61c8203b0bd924/src/messaging/ExchangeContext.cpp#L491
https://github.com/project-chip/connectedhomeip/blob/a6ecd62777cd2d9646f13d809b61c8203b0bd924/src/messaging/ReliableMessageMgr.cpp#L150
For consistency, it would be nice if this also happened when marking sessions defunct due to subscription liveliness timeout here:
https://github.com/project-chip/connectedhomeip/blob/a6ecd62777cd2d9646f13d809b61c8203b0bd924/src/app/ReadClient.cpp#L874
A simple approach may be to emit the event from the SecureSession itself whenever the session is marked kDefunct, as we do for MarkForEviction:
https://github.com/project-chip/connectedhomeip/blob/a6ecd62777cd2d9646f13d809b61c8203b0bd924/src/transport/SecureSession.cpp#L149
Platform
core
Platform Version(s)
No response
Anything else?
No response

That said, there are places where we MarkAsDefunct because of something on our end (various "Disconnect"-like APIs), and those should probably not OnSessionHang.
Also not sure we should OnSessionHang in ReadClient::OnLivenessTimeoutCallback for the sessions that are not the one we were expecting a message on (but have been idle for at least as long).

On reflection, I don't think this is feasible.  The problem is that the ReadClient cannot know whether its subscription has timed out because another ReadClient has sent a request with keep-subscriptions=false.  If one has, subscription timeout does not indicate session disappearance.
Only code that has view of all of the ReadClients and which has serialized subscription requests (which also requires waiting for responses before issuing new subscription requests because Matter secure channel comms aren't inherently ordered) can make this inference.  Code that does have this view can itself emit OnSessionHang if it knows all of the above and sees the client OnError with CHIP_ERROR_TIMEOUT.
@bzbarsky-apple 's point is also well taken: a subscription could survive across multiple sessions; there is no way for the read client to know whether the SessionHolder in the client that was used to establish the subscription is still relevant.  So code emitting session hang would also need to tie this together.
Hence, closing.


macro paradise

is any support for scala macros ?

Some support (or documentation) around scala compiler plugins would be handy
Currently we use macro Paradise as well as WartRemover, while the latter we can probably live without, we need the former.
there is a workaround listed https://discuss.gradle.org/t/how-to-apply-scala-macro-paradise-plugin/9316/6 but I haven't yet tested it with Android.


Overhauled Input trait to improve versatility, added IterInput

This PR does a few things:

Improves the design of Input, allowing is to support a wider array of input types (see the new IterInput)
Gives inputs mutable access to part of their cached state, removing the need for Cell/RefCell in existing input implementations
Removes the Sealed bound from all input types except StrInput, allowing users to implement their own input types

Review/thoughts welcome!
If you don't want to look at the whole diff, the important part is the new definition of Input.
The performance implications are unclear: Some benchmarks are slightly faster, some are slightly slower. I don't think it's notable enough to matter.

The more I think about this, the more I'm confident that this MR is broadly the right thing to do, so I'm going to merge it to avoid unnecessary rebasing work. Post-merge review is still welcome and useful though!


Add Transaction Status Updated webhook

Adding support for the Transaction Status Updated Webhook.
Recurly Documentation

I noticed that tests were failing on master, so I fixed those in https://github.com/blacklightcms/recurly/pull/144.
I'll wait on this PR until that one's merged in.

@cristiangraz, could you please take a look at this and #144 when you have a chance?
Thanks in advance.


Default Full Width and/or small text for all Pages.

problem
I personally set all my pages to be full width so I can see as much as possible on a certain page. The problem is that Notion doesn't have default settings so for every new page we have to set them separately.

solution
It would be great to be able to set the default settings within the enhancer that should be applied to all new pages that are created.

it won't change the actual setting, but you can make all pages appear full width by adding the following with the custom inserts plugin:
:root {
  --theme_dark--page_normal-width: 100%;
  --theme_light--page_normal-width: 100%;
}

it won't change the actual setting, but you can make all pages appear full width by adding the following with the custom inserts plugin:
:root {
  --theme_dark--page_normal-width: 100%;
  --theme_light--page_normal-width: 100%;
}

most of the enhancer's functions are just visual. it can't reliably modify actual page/account data yet.

How do we download the copy inserts plugin?

@safwaan-menk all mods come with the notion-enhancer when you install it. The custom inserts and tweak's mods have since been merged, though - now you can upload your custom CSS file to the css insert option under the tweaks extension.

@safwaan-menk all mods come with the notion-enhancer when you install it. The custom inserts and tweak's mods have since been merged, though - now you can upload your custom CSS file to the css insert option under the tweaks extension.

If I create a css file with only the below code, which you gave, would it achieve the full width facade?
:root {   --theme_dark--page_normal-width: 100%;   --theme_light--page_normal-width: 100%; }

@safwaan-menk probably not, the css variables available for customisation have changed. This issue thread has been closed for over 2 years, so it's very outdated. You can find the full list of available variables and their default values in this CSS file that you can customise as you like, though some of them aren't working perfectly at the moment due to Notion updates: https://github.com/notion-enhancer/repo/blob/9c869179b39dc11e07d6b6200b3ebd8d344cde16/theming/variables.css