Staging2 merge to live-based

Version(s) of document impacted

[ ] Impacts 7 document
[ ] Impacts 6 document
[ ] Impacts 5.1 document
[ ] Impacts 5.0 document
[ ] Impacts 4.0 document
[ ] Impacts 3.0 document

Reason(s) for not updating all version of documents

[ ] The documented feature was introduced in version (list version here) of PowerShell
[ ] This issue only shows up in version (list version(s) here) of the document
[ ] This PR partially fixes the issue, and issue # tracks the remaining work

Docs Build status updates of commit f8d2281:
:clock10: Pending: waiting for processors (8 builds ahead of you)
:warning: Docs Build is busy, currently there are 8 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

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

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-Prod/PowerShell-Docs, working directory: W:\h0o1-s, target branch: live-based, target branch commit: e4d156aea8e6f8196639953ecf138a79bd562417, source commit: f8d2281b7b018e52cfbe5ece2c4b56f730605ba4.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 6474e9f:
:clock10: Pending: waiting for processors (14 builds ahead of you)
:warning: Docs Build is busy, currently there are 14 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 6474e9f:
:warning: Validation status: warnings

File
Status
Preview URL
Details

developer/prog-guide/runspace03-code-samples.md
:warning:Warning
View
Details

developer/prog-guide/runspace03-csharp-code-sample.md
:warning:Warning
View
Details

developer/prog-guide/runspace03-vb-net-code-sample.md
:warning:Warning
View
Details

developer/prog-guide/windows-powershell-sample-code.md
:warning:Warning
View
Details

reference/3.0/Microsoft.PowerShell.Core/About/About.md
:warning:Warning
View (powershell-3.0)
Details

reference/3.0/Microsoft.PowerShell.Core/About/about_For.md
:warning:Warning
View (powershell-3.0)
Details

reference/3.0/Microsoft.PowerShell.Core/About/about_Functions_Advanced_Parameters.md
:warning:Warning
View (powershell-3.0)
Details

reference/3.0/Microsoft.PowerShell.Core/About/about_Line_Editing.md
:warning:Warning
View (powershell-3.0)
Details

reference/3.0/Microsoft.PowerShell.Core/About/about_Operator_Precedence.md
:warning:Warning
View (powershell-3.0)
Details

reference/3.0/Microsoft.PowerShell.Core/About/about_PowerShell_exe.md
:warning:Warning
View (powershell-3.0)
Details

reference/3.0/Microsoft.PowerShell.Core/About/about_Registry_Provider.md
:warning:Warning
View (powershell-3.0)
Details

reference/3.0/Microsoft.PowerShell.Core/About/about_Regular_Expressions.md
:warning:Warning
View (powershell-3.0)
Details

reference/3.0/Microsoft.PowerShell.Core/About/about_Remote_Variables.md
:warning:Warning
View (powershell-3.0)
Details

reference/3.0/Microsoft.PowerShell.Core/About/about_Requires.md
:warning:Warning
View (powershell-3.0)
Details

reference/3.0/Microsoft.PowerShell.Core/About/about_Session_Configurations.md
:warning:Warning
View (powershell-3.0)
Details

reference/3.0/Microsoft.PowerShell.Core/About/about_Type_Operators.md
:warning:Warning
View (powershell-3.0)
Details

reference/3.0/Microsoft.PowerShell.Core/About/about_Updatable_Help.md
:warning:Warning
View (powershell-3.0)
Details

reference/3.0/Microsoft.PowerShell.Security/About/about_Certificate_Provider.md
:warning:Warning
View (powershell-3.0)
Details

reference/3.0/PSWorkflow/About/about_Foreach-Parallel.md
:warning:Warning
View (powershell-3.0)
Details

reference/3.0/PSWorkflow/About/about_InlineScript.md
:warning:Warning
View (powershell-3.0)
Details

reference/3.0/PSWorkflow/About/about_Sequence.md
:warning:Warning
View (powershell-3.0)
Details

reference/3.0/PSWorkflow/About/about_Suspend-Workflow.md
:warning:Warning
View (powershell-3.0)
Details

reference/3.0/PSWorkflow/About/about_Workflows.md
:warning:Warning
View (powershell-3.0)
Details

reference/4.0/Microsoft.PowerShell.Core/About/About.md
:warning:Warning
View (powershell-4.0)
Details

reference/4.0/Microsoft.PowerShell.Core/About/about_For.md
:warning:Warning
View (powershell-4.0)
Details

reference/4.0/Microsoft.PowerShell.Core/About/about_Functions_Advanced_Parameters.md
:warning:Warning
View (powershell-4.0)
Details

reference/4.0/Microsoft.PowerShell.Core/About/about_Line_Editing.md
:warning:Warning
View (powershell-4.0)
Details

reference/4.0/Microsoft.PowerShell.Core/About/about_Operator_Precedence.md
:warning:Warning
View (powershell-4.0)
Details

reference/4.0/Microsoft.PowerShell.Core/About/about_Registry_Provider.md
:warning:Warning
View (powershell-4.0)
Details

reference/4.0/Microsoft.PowerShell.Core/About/about_Regular_Expressions.md
:warning:Warning
View (powershell-4.0)
Details

reference/4.0/Microsoft.PowerShell.Core/About/about_Remote_Variables.md
:warning:Warning
View (powershell-4.0)
Details

reference/4.0/Microsoft.PowerShell.Core/About/about_Requires.md
:warning:Warning
View (powershell-4.0)
Details

reference/4.0/Microsoft.PowerShell.Core/About/about_Session_Configurations.md
:warning:Warning
View (powershell-4.0)
Details

reference/4.0/Microsoft.PowerShell.Core/About/about_Type_Operators.md
:warning:Warning
View (powershell-4.0)
Details

reference/4.0/Microsoft.PowerShell.Core/About/about_Updatable_Help.md
:warning:Warning
View (powershell-4.0)
Details

reference/4.0/Microsoft.PowerShell.Core/About/about_desiredstateconfiguration.md
:warning:Warning
View (powershell-4.0)
Details

reference/4.0/Microsoft.PowerShell.Security/About/about_Certificate_Provider.md
:warning:Warning
View (powershell-4.0)
Details

reference/4.0/PSWorkflow/About/about_Foreach-Parallel.md
:warning:Warning
View (powershell-4.0)
Details

reference/4.0/PSWorkflow/About/about_InlineScript.md
:warning:Warning
View (powershell-4.0)
Details

reference/4.0/PSWorkflow/About/about_Sequence.md
:warning:Warning
View (powershell-4.0)
Details

reference/4.0/PSWorkflow/About/about_Suspend-Workflow.md
:warning:Warning
View (powershell-4.0)
Details

reference/4.0/PSWorkflow/About/about_Workflows.md
:warning:Warning
View (powershell-4.0)
Details

reference/5.0/Microsoft.PowerShell.Core/About/About.md
:warning:Warning
View (powershell-5.0)
Details

reference/5.0/Microsoft.PowerShell.Core/About/about_Alias_Provider.md
:warning:Warning
View (powershell-5.0)
Details

reference/5.0/Microsoft.PowerShell.Core/About/about_Environment_Provider.md
:warning:Warning
View (powershell-5.0)
Details

reference/5.0/Microsoft.PowerShell.Core/About/about_FileSystem_Provider.md
:warning:Warning
View (powershell-5.0)
Details

reference/5.0/Microsoft.PowerShell.Core/About/about_For.md
:warning:Warning
View (powershell-5.0)
Details

reference/5.0/Microsoft.PowerShell.Core/About/about_Function_Provider.md
:warning:Warning
View (powershell-5.0)
Details

reference/5.0/Microsoft.PowerShell.Core/About/about_Functions_Advanced_Parameters.md
:warning:Warning
View (powershell-5.0)
Details

reference/5.0/Microsoft.PowerShell.Core/About/about_Line_Editing.md
:warning:Warning
View (powershell-5.0)
Details

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

developer/prog-guide/runspace03-code-samples.md

Line 14: [Warning] Invalid file link:(~/prog-guide/fd).

developer/prog-guide/runspace03-csharp-code-sample.md

Line 14: [Warning] Invalid file link:(~/prog-guide/fd).

developer/prog-guide/runspace03-vb-net-code-sample.md

Line 14: [Warning] Invalid file link:(~/prog-guide/fd).

developer/prog-guide/windows-powershell-sample-code.md

Line 38: [Warning] Invalid file link:(~/prog-guide/fd).

reference/3.0/Microsoft.PowerShell.Core/About/About.md

[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 3.0/Microsoft.PowerShell.Core/About/About.md

reference/3.0/Microsoft.PowerShell.Core/About/about_For.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/3.0/Microsoft.PowerShell.Core/About/about_Functions_Advanced_Parameters.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/3.0/Microsoft.PowerShell.Core/About/about_Line_Editing.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/3.0/Microsoft.PowerShell.Core/About/about_Operator_Precedence.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/3.0/Microsoft.PowerShell.Core/About/about_PowerShell_exe.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/3.0/Microsoft.PowerShell.Core/About/about_Registry_Provider.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/3.0/Microsoft.PowerShell.Core/About/about_Regular_Expressions.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/3.0/Microsoft.PowerShell.Core/About/about_Remote_Variables.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/3.0/Microsoft.PowerShell.Core/About/about_Requires.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/3.0/Microsoft.PowerShell.Core/About/about_Session_Configurations.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/3.0/Microsoft.PowerShell.Core/About/about_Type_Operators.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/3.0/Microsoft.PowerShell.Core/About/about_Updatable_Help.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/3.0/Microsoft.PowerShell.Security/About/about_Certificate_Provider.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/3.0/PSWorkflow/About/about_Foreach-Parallel.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/3.0/PSWorkflow/About/about_InlineScript.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/3.0/PSWorkflow/About/about_Sequence.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/3.0/PSWorkflow/About/about_Suspend-Workflow.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/3.0/PSWorkflow/About/about_Workflows.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/4.0/Microsoft.PowerShell.Core/About/About.md

[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 4.0/Microsoft.PowerShell.Core/About/About.md

reference/4.0/Microsoft.PowerShell.Core/About/about_For.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/4.0/Microsoft.PowerShell.Core/About/about_Functions_Advanced_Parameters.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/4.0/Microsoft.PowerShell.Core/About/about_Line_Editing.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/4.0/Microsoft.PowerShell.Core/About/about_Operator_Precedence.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/4.0/Microsoft.PowerShell.Core/About/about_Registry_Provider.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/4.0/Microsoft.PowerShell.Core/About/about_Regular_Expressions.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/4.0/Microsoft.PowerShell.Core/About/about_Remote_Variables.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/4.0/Microsoft.PowerShell.Core/About/about_Requires.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/4.0/Microsoft.PowerShell.Core/About/about_Session_Configurations.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/4.0/Microsoft.PowerShell.Core/About/about_Type_Operators.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/4.0/Microsoft.PowerShell.Core/About/about_Updatable_Help.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/4.0/Microsoft.PowerShell.Core/About/about_desiredstateconfiguration.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/4.0/Microsoft.PowerShell.Security/About/about_Certificate_Provider.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/4.0/PSWorkflow/About/about_Foreach-Parallel.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/4.0/PSWorkflow/About/about_InlineScript.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/4.0/PSWorkflow/About/about_Sequence.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/4.0/PSWorkflow/About/about_Suspend-Workflow.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/4.0/PSWorkflow/About/about_Workflows.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/5.0/Microsoft.PowerShell.Core/About/About.md

[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md
[Warning] Can't find service name for 5.0/Microsoft.PowerShell.Core/About/About.md

reference/5.0/Microsoft.PowerShell.Core/About/about_Alias_Provider.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/5.0/Microsoft.PowerShell.Core/About/about_Environment_Provider.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/5.0/Microsoft.PowerShell.Core/About/about_FileSystem_Provider.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/5.0/Microsoft.PowerShell.Core/About/about_For.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/5.0/Microsoft.PowerShell.Core/About/about_Function_Provider.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/5.0/Microsoft.PowerShell.Core/About/about_Functions_Advanced_Parameters.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

reference/5.0/Microsoft.PowerShell.Core/About/about_Line_Editing.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Can not set up Azure Dev Ops as bug tracker (automatically transferred HockeyApp account)

For both my colleague and me, we can not hook Azure Dev Ops as bug tracker service for Android project
We are both admins of the app in AppCenter
I am admin of the project on Azure Dev Ops, he is admin of the whole organization in Azure Dev Ops, so the issue shouldn't be there even if we receive error that we don't have permissions
Maybe the issue lies in the fact that our accounts initially existed on HockeyApp, and we used HockeyApp login there, while to Azure Dev Ops and App Center we log in with organization Azure AD
Even if the AppCenter gives us ability to login with Azure AD account SSO, maybe it still treats it as HockeyApp account and that is why we don't have sufficient permissions (we see that it says HockeyApp account in profile in AppCenter)

We used steps from https://docs.microsoft.com/en-us/appcenter/dashboard/bugtracker/

I succeed to list the projects and when I get to final step to click "Add" I get the user 'XXXXXXXX-7a39-61c3-b81c-XXXXXXX' is not authorized to access this resource.

Hey @brcinho - have you moved your HockeyApp apps to App Center? There are some settings that can't be managed or changed in App Center until you officially migrate your apps over: https://docs.microsoft.com/en-us/appcenter/transition/moving/
Let me know if that works!

That app wasn't transferred from HockeyApp, it was newly created in AppCenter, the user account on the other hand was transferred and that is what could be causing the issue. Can someone from your support team flag the account as Azure AD account in AppCenter (instead of being marked as HockeyApp account) even if I loose the links in AppCenter to things in HockeyApp.
We will not use "Transfer app" feature in AppCenter because we have enterprise clients which have very slow pace of moving to newer version of apps. We already created all new apps in AppCenter for our needs.

@brcinho whether your account originates from HockeyApp or not has nothing to do with Azure DevOps. It simply is a flag that shows or hides certain functionality from the UI. However, your problem is not connected to your account but to the app level.
Please reach out to us in support so we can better investigate the issue.

Hi @derpixeldan Where to reach you in support? I already utilized the chat button in AppCenter to report this issue and currently am participating in one thread with support. Is that what you meant?

@brcinho yes, that's what I meant. I found your ticket and will follow up there.

Closing as it was addressed via support.


Add dial codes into data.json

This is super awesome!
Could I get you to pull in the latest changes (#3) and add the dial code for that?

@matiassingers
Thanks, I've added the dial code for Kosovo 👍

Awesome stuff, thanks so much again @selahattinunlu!


Fails to read larger QR code Versions

The component (I've tried it myself and also on the demo page), can detect the presence of larger QR code versions but the returned data is empty.
It fails to read the following QR code, yet https://zxing.org/w/decode.jspx can.

I think the problem might be the encoding or some other mode. Here is the technical details of this QR:
- Version 15 (77x77 modules).
- Byte data (Mode Byte, Binary).
- ECC (and ECL) level M (Error Correction Level M).
- ECI (Extended Channel Interpretation).
- (ECI value 000004)
- encoding ISO-8859-2.
- module size 0,42333 mm x 0,42333 mm.
- code size 32,59676 mm x 32,59667 mm.

perhaps the encoding here is the problem?

Thanks for the detailed report!

Yeah, I changed from jsQR to zxing-js for my QR reader


Add CI badge

Will investigate the flaky test 🕵

Will investigate the flaky test 🕵

@fbiville thank you so much!!!

@fbiville thank you so much!!!


Compilation error: invalid conversion from 'void*' to 'lv_style_anim_dsc_t*' in lv_style.h

When compiling with lvgl 6.0 (commit  d79df21) the following error is given in Arduino 1.8.9:
 In file included from C:\Users\xxx\Documents\onedrive\Arduino\libraries\lv_arduino/src/lv_core /lv_obj.h:24:0,

 from C:\Users\xxx\Documents\onedrive\Arduino\libraries\lv_arduino/lvgl.h:25,

 from C:\Users\xxx\Documents\OneDrive\Arduino\projects\STM32\V6.0\LittlevGL_Spinbox\LittlevGL_Spinbox.ino:1:

 C:\Users\xxx\Documents\onedrive\Arduino\libraries\lv_arduino/src/lv_core/lv_style.h: In function 'void lv_style_anim_set_ready_cb(lv_anim_t*, lv_anim_ready_cb_t)':

 C:\Users\xxx\Documents\onedrive\Arduino\libraries\lv_arduino/src/lv_core/lv_style.h:188:36: error: invalid conversion from 'void*' to 'lv_style_anim_dsc_t*' [-fpermissive]

 lv_style_anim_dsc_t * dsc = a->var;

Perhaps a cast is needed?

Just fixed it. Thanks: https://github.com/littlevgl/lvgl/commit/7f7034f50fd62b3a3335e72510e129dab4cc3745
C doesn't usually care, but C++ is picky about conversions from void * without casting.

Thank you!


Added NSCoding to OAuthSwiftCredential for easy storage in the Keychain.

SwiftKeychainWrapper, and other such keychain wrappers, allow for easily storing an retrieving NSCoding-compatible objects in the keychain. OAuthSwiftCredential could benefit from some NSCoding love.

Hi @harlanhaskins
I tried with the following code
NSKeyedArchiver.archiveRootObject(credential, toFile: path)

Thank you!


Tweaks git checkout UI output

Tweaking the "Updating ..." output of the checkout method to reduce
confusion when running outdated. Opting instead for "Fetching" as it
does when doing a clone operation.

@homu r+

:pushpin: Commit b22f0f4 has been approved by indirect

:hourglass: Testing commit b22f0f4 with merge b3f9d0f...

:sunny: Test successful - status


Add Norway East for AZ support

@zhenlan : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@AlexandraKemperMS can you please review?

#sign-off


Code

Hello)
How soon do you plan to release the code? Looking forward for it, thanks for your work

Hello?)

又一个僵尸项目。以后对于没开源的就不细看论文了

Nice work! +1 request

想看code

When will the code be released, looking forward for it!!! qwq qwq

If the code's are not released at all, we should regard the paper's correctness to be not grounded well. I don't think this paper works as authors claimed.

The code has been released. Greatly sorry for the very late time to release the codes.


CDATA is stripped

Lambda Soup seems to have no notion of CDATA, and therefore ends up stripping its contents. For instance the following code:
printf
  "%s"
  ("
Hi<![CDATA[[Something or other]]>
"
   |> Lambda_soup.Soup.parse
   |> Lambda_soup.Soup.to_string);

results in:

Hi

But I would have expected:

Hi Something or other

or something similar.

@jsomers, CDATA is not allowed in HTML5. It is only allowed in "foreign elements" (SVG, MathML, etc.) embedded in HTML. If CDATA is found in HTML, the parser is supposed to treat it as a comment. From https://www.w3.org/TR/html52/syntax.html#markup-declaration-open-state (after reading <!):

Otherwise, if there is an adjusted current node and it is not an element in the HTML namespace and the next seven characters are a case-sensitive match for the string "[CDATA[" (the five uppercase letters "CDATA" with a U+005B LEFT SQUARE BRACKET character before and after), then consume those characters and switch to the CDATA section state.
Otherwise, this is a parse error. Create a comment token whose data is the empty string. Switch to the bogus comment state (don’t consume anything in the current state).

@aantron Ah, maybe my example was misleading, because the real tag that had the CDATA in it was not in the HTML namespace: <ac:plain-text-body><![CDATA[[content was here]]></ac:plain-text-body>.
In this case the characters are being stripped, too, but it sounds like from the spec you've quoted that they're supposed to be consumed in some kind of special mode (and therefore that they should be retrievable somehow)?
Thanks!

What language is that tag from?
"Standard" HTML5 only allows HTML, SVG, and MathML, does not recognize xmlns declarations, and treats all elements that aren't in <svg> or <math> as generic, unknown HTML elements in the HTML namespace. See the note a bit down in this section: https://www.w3.org/TR/html52/syntax.html#writing-html-documents-elements.
Here's another: https://www.w3.org/TR/html52/syntax.html#cdata-sections, CDATA sections allowed only in MathML and SVG. Per the previous paragraph, HTML5 has a pretty restricted way of knowing when content is MathML or SVG.
There are a couple more sections about this, but the spec is pretty convoluted and I don't want to dump the whole reasoning out here :)
I don't mean to stick too closely to the spec. It may be worthwhile to support this. Perhaps we can modify the parser so that it takes an optional parameter that enables CDATA in HTML.

Yes, they should be available in a comment, but Lambda Soup drops comments :) Perhaps we need to keep comments instead.

That would be great!

What language is that tag from?

It's emitted by a wiki product called Atlassian Confluence, which is in wide use. Their use of CDATA is definitely bizarre, but it would be great if it were at least possible to get at it via Lambda Soup.
Thanks :smile:

@jsomers Is Atlassian Conference emitting HTML or XML? If HTML, is it well-formed enough to pass as XML? I ask because if that's the case, it should be possible to process the input as XML using Lambda Soup's underlying parser, with some variation of this: http://aantron.github.io/lambda-soup/#VALfrom_signals. That way, we can avoid adding quirks handling for some app's non-standard-compliant output :)

@aantron It's technically XML, but they call it "XHTML-based" because it's mostly HTML with some custom (non-spec-compliant) stuff thrown in.

@jsomers, that's good news, and I'm glad Atlassian documents what format they actually produce. You should be able to parse it, with CDATA, by
let soup =
  Markup.string your_xml_string |> Markup.parse_xml |> Markup.signals |> Soup.from_signals in
...

The resulting value will be a Soup.(soup node), the same type as if you had used Soup.parse your_xml_string, except this code parses the string as XML instead of HTML5, so it should be more appropriate to the inputs you have.

@aantron, got it, that works---thanks very much! Feel free to close the issue.

Excellent!


Add NPS Result component

Change summary
Added a new component

Change type

[ ] No review
[X] Small PR
[ ] Big PR
[ ] Refactor

Closes https://app.clickup.com/t/9004075864/DIGI-896

Merging after resolving comments as discussed with Gerard.


Changing Damage types for Versatile weapons

Pretty sure this is easier said then done.
It is rather clunky to change the damage types for Versatile weapons. It would be great if when rolling damage, for versatile weapons, it prompts you for what damage type it should be then does the roll.

Now that IWR is in, tons of people are asking for this.  I think something well designed is planned for the future.
But in the meantime, you can add REs that make toggles, which you can set before rolling damage.  Any toggle can be dragged from the character sheet actions tab to the macro bar to make a toggle macro.  So this is reasonable convenient to use.  Just have to remember that you wanted to change before you roll.
Add to a weapon, or a deity boon or feat.  The toggles will affect all your appropriately versatile weapons.
{"key":"DamageDice","selector":"damage","override":{"damageType":"piercing"},"predicate":["item:trait:versatile-p","use-versatile-p"]}
{"key":"DamageDice","selector":"damage","override":{"damageType":"slashing"},"predicate":["item:trait:versatile-s","use-versatile-s"]}
{"key":"DamageDice","selector":"damage","override":{"damageType":"bludgeoning"},"predicate":["item:trait:versatile-b","use-versatile-b"]}
{"key":"RollOption","option":"use-versatile-p","label":"Use versatile Piercing damage","domain":"damage-roll","toggleable":true}
{"key":"RollOption","option":"use-versatile-s","label":"Use versatile Slashing damage","domain":"damage-roll","toggleable":true}
{"key":"RollOption","option":"use-versatile-b","label":"Use versatile Bludgeoning damage","domain":"damage-roll","toggleable":true}

Thank you very much, I'll play around with it. And have my fingers crossed for this feature to be added sometime.

here's a premade feat to import with just those 6 REs on it.

here's a premade feat to import with just those 6 REs on it.

Thank you

Here's the same thing from above adapted for the Modular B, P, or S trait
{"key":"DamageDice","selector":"damage","override":{"damageType":"piercing"},"predicate":["item:trait:modular","use-modular-p"]}
{"key":"DamageDice","selector":"damage","override":{"damageType":"slashing"},"predicate":["item:trait:modular","use-modular-s"]}
{"key":"DamageDice","selector":"damage","override":{"damageType":"bludgeoning"},"predicate":["item:trait:modular","use-modular-b"]}
{"key":"RollOption","option":"use-modular-p","label":"Use modular Piercing damage","domain":"damage-roll","toggleable":true}
{"key":"RollOption","option":"use-modular-s","label":"Use modular Slashing damage","domain":"damage-roll","toggleable":true}
{"key":"RollOption","option":"use-modular-b","label":"Use modular Bludgeoning damage","domain":"damage-roll","toggleable":true}


Add type attribute to _package.json

Part of #316
This PR adds the attribute type in the _package.json files to be able to differentiate between the latest, historical, and the dev version once is implemented.
This new attribute will be used to determine when to add a label in the version selector of the API docs

Closed in favor of using the path to determine the type of each version instead of adding a new attribute to the _package.json


Raidboss: Dungeons ST: ala_mhigo, drowned_city_of_skalla and temple_of_the_fist FR

translations corrections and added missing fr => temple_of_the_fist
translations corrections fr => drowned_city_of_skalla
added missing translations fr + removal missingTranslations => ala_mhigo
for ala_mhigo, i have did the dungeon, but on my logs, it's same written 'Unknown_206E'. it's usefull to see it in timeline ?

I removed Unknown_206E from the timeline if you want to remove it here.

Thanks !


Ubuntu AndroidStudio flutter: JAVA_HOME is not set

I'm having a problem running my flutter application in android studio.
It gives me the following message
Launching lib/main.dart on sdk gphone x86 in debug mode...
Running Gradle task 'assembleDebug'...

ERROR: JAVA_HOME is not set and no 'java' command could be found in your PATH.

Please set the JAVA_HOME variable in your environment to match the
location of your Java installation.

Exception: Gradle task assembleDebug failed with exit code 1

Here is echo $JAVA_HOME and I have added the bin to my PATH
/usr/lib/jvm/openjdk-14.0.2_linux-x64_bin/jdk-14.0.2

I can run flutter from terminal via flutter run after upgrading gradle from gradle-5.6.2-all.zip to gradle-6.3-all.zip
I think the problem lies in android/gradlew in the following script
# Determine the Java command to use to start the JVM.
if [ -n "$JAVA_HOME" ] ; then
    if [ -x "$JAVA_HOME/jre/sh/java" ] ; then
        # IBM's JDK on AIX uses strange locations for the executables
        JAVACMD="$JAVA_HOME/jre/sh/java"
    else
        JAVACMD="$JAVA_HOME/bin/java"
    fi
    if [ ! -x "$JAVACMD" ] ; then
        die "ERROR: JAVA_HOME is set to an invalid directory: $JAVA_HOME

Please set the JAVA_HOME variable in your environment to match the
location of your Java installation."
    fi
else
    JAVACMD="java"
    which java >/dev/null 2>&1 || die "ERROR: JAVA_HOME is not set and no 'java' command could be found in your PATH.

Please set the JAVA_HOME variable in your environment to match the
location of your Java installation."
fi

I tried copying it and running it and it runs with no problems with #!/usr/bin/env bash which is the shebang in gradlew
I tried reinstalling android studio, but it didn't work. My flutter doctor --verbose is a mess. At first it couldn't find android studio- said it is not installed. so I ran flutter config --android-studio-dir="/snap/bin" but now I get this output even though I have the plugins installed
:~$ flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 1.22.4, on Linux, locale en_US.UTF-8)
[!] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/linux#android-setup for more details.
[!] Android Studio
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    ✗ android-studio-dir = /snap/bin
    ✗ Unable to find bundled Java version.
[!] Connected device
    ! No devices available

! Doctor found issues in 3 categories.
:~$ flutter doctor --android-licenses
Exception in thread "main" java.lang.NoClassDefFoundError: javax/xml/bind/annotation/XmlSchema
	at com.android.repository.api.SchemaModule$SchemaModuleVersion.<init>(SchemaModule.java:156)
	at com.android.repository.api.SchemaModule.<init>(SchemaModule.java:75)
	at com.android.sdklib.repository.AndroidSdkHandler.<clinit>(AndroidSdkHandler.java:81)
	at com.android.sdklib.tool.sdkmanager.SdkManagerCli.main(SdkManagerCli.java:73)
	at com.android.sdklib.tool.sdkmanager.SdkManagerCli.main(SdkManagerCli.java:48)
Caused by: java.lang.ClassNotFoundException: javax.xml.bind.annotation.XmlSchema
	at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:602)
	at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
	at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:522)
	... 5 more

Thank you all hopefully I'm missing something simple!

Here is flutter doctor with the --verbose flag
[✓] Flutter (Channel stable, 1.22.4, on Linux, locale en_US.UTF-8)
    • Flutter version 1.22.4 at /opt/flutter_linux_1.20.4-stable/flutter
    • Framework revision 1aafb3a8b9 (5 hours ago), 2020-11-13 09:59:28 -0800
    • Engine revision 2c956a31c0
    • Dart version 2.10.4

[!] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at /home/moneer/Android/Sdk
    • Platform android-30, build-tools 30.0.2
    • Java binary at:
      /usr/lib/jvm/openjdk-14.0.2_linux-x64_bin/jdk-14.0.2/bin/java
    • Java version OpenJDK Runtime Environment (build 14.0.2+12-46)
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/linux#android-setup for
      more details.

[!] Android Studio
    • Android Studio at /snap/bin
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    ✗ android-studio-dir = /snap/bin
    ✗ Unable to find bundled Java version.
    • Try updating or re-installing Android Studio.
    • Consider removing your android-studio-dir setting by running:
      flutter config --android-studio-dir=

[!] Connected device
    ! No devices available

! Doctor found issues in 3 categories.

@moneer-muntazah   seems like you are using open 14 instead of 8
here is the easy part
sudo apt-get remove --auto-remove openjdk*
sudo apt-get install openjdk-8-jre
gedit ~/bashrc

make sure that your path looks like this
export PATH="$PATH:/snap/bin/flutter/bin"
export PATH="$PATH:/usr/bin/java"
export JAVA_HOME=/usr/lib/jvm/java-1.8.0-openjdk-amd64/jre
export ANDROID_SDK_ROOT=/home/<YOUR USER NAME>/Android/Sdk

then run
source ~/bashrc
flutter docrtor -v

here comes the bad news...
you might have trouble to get android studio recognized
https://github.com/canonical/flutter-snap/issues/16

@moneer-muntazah
sorry... my bad
to fix android studio just run
flutter config --android-studio-dir=/snap/android-studio/current/android-studio

After upgrading to Android studio 4.1.1, I had a couple of  issues and fixed by:

$ flutter upgrade
$ flutter config --android-studio-dir="/path/to/android/studio/"

$ vim ~/.bashrc
export JAVA_HOME="/path/to/android/studio/jre/"

$ vim pubspec.yaml
dependency_overrides:
   intl: ^0.17.0-nullsafety.2

All Possible Working Solution Added Here [Solved] ERROR: JAVA_HOME is not set and no ‘java’ command could be found in your flutter PATH. in flutter


Slides: Python from the Shell

We don't seem to have much prior art to draw on here.
@bradleyboehmke / @eswan18 / @augustopher, what kind of topics did you have in mind here? Possibilities:

Running Python from the command line
Creating virtual environments
The subprocess module for running scripts from Python
Using argparse to parse command line arguments

Never mind, found this in the intermediate class:
https://github.com/uc-python/intermediate-python-datasci/blob/master/notebooks/06-Python_from_the_Shell.ipynb


upload/download-artifact v2 will be deprecated on June 30, 2024

https://github.com/actions/upload-artifact

actions/upload-artifact@v3 is scheduled for deprecation on November 30, 2024. Learn more. Similarly, v1/v2 are scheduled for deprecation on June 30, 2024. Please update your workflow to use v4 of the artifact actions. This deprecation will not impact any existing versions of GitHub Enterprise Server being used by customers.

This repo uses a mix of v2 and v3.
AB#2783504

Fixed by #367


apply to evonorm1d(sequence data)

Hi, i have read your code,but i want to know whether evo_norm could be used for sequence-data, for example, the dims in data just likes batch_size, seq_len, embedding_dims.
In other words, N, C, H, W = x.size(),  does C correspond to embedding_dims?

@small-Qing for sequence data, we would have to implement a version Evonorm1d since the 2d version expects a 4-dimensional tensor of the shape <N,C,H,W>. This shouldn't be that difficult to implement, but I can't commit to building it in the next 2 weeks.


python3.pkgs.jupysql: disable broken tests due to duckdb>=1.1.0

Disable a few tests for jupysql seemingly caused by later versions of duckdb (>=1.1.0)
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

packages built:
python311Packages.jupysql python311Packages.jupysql.dist python312Packages.jupysql python312Packages.jupysql.dist
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 352864

x86_64-linux

:white_check_mark: 4 packages built:

python311Packages.jupysql
python311Packages.jupysql.dist
python312Packages.jupysql
python312Packages.jupysql.dist

@Aleksanaa Would you mind merging this one too?

@ofborg build python311Packages.jupysql python312Packages.jupysql


Better outline tree settings/functionality for tree depth and expand/collapse functionality

It would be amazing if double-clicking an item in the Outline ListTree functioned the same as clicking on its corresponding twistie!
Use Case:
The reason I would prefer this is that by default I personally find that expanding the entire tree out to display down to the function variables to be excessive and hard to find what I'm looking for.
Due to this I almost always do a collapse all and then expand down to showing all functions in a class.
Alternate (and preferred) Possible "Fix":
Provide a setting to determine how deep a user wants the tree to expand. Providing something like this would nearly eliminate the need for me to modify the depth of the tree almost entirely!

On trees such as the Outline one, clicking the twistie while holding the Alt key down (I'm on Windows) makes an expand act on multiple levels, and ditto a coollapse.

That is handy, however, that ends up getting me back to the view which triggered the feature request. The "ideal" solution for me is still that a setting gets added to allow me to specify the depth that the Outline panel is expanded by default.
I'd be much happy with the option to double click an item in the tree to trigger an expand or collapse.

The recent changes in the default outline display has degraded it's usability.
Originally when opening a file the Outline would by default display the functions which was perfect, or the classes and functions. I'm always looking for a particular function in a file, and having them listed alphabetical is perfect. (I normally have only a single class per file so in general I only have a single list of functions for each file).
The current version however lists all functions constants and variables, this is really long as my files can be quite large (lots of functions). So I use the "collapse" button - this works in a file that only contains functions - the functions are all listed alphabetically. But in a class file the collapse function then shows all of the classes, and generally I only have one class per file, so it lists one class name. I then have to expand the class to see the functions. This is 2 clicks more than I want.
Can we please have the outline default to listing functions only?  Or as Jared suggests, an option we can set indicating a default depth.

@Jared-Dev Is this an Outline specific feature request, or any trees?

@Jared-Dev Is this an Outline specific feature request, or any trees?

The Outline tree is where I have the issue personally so, at the moment, I don't see a need to expand the functionality outside of this.

Let me try to summarize:

If the user clicks the twistie, the node expands/collapses
If the user clicks the row, the editor line is selected and revealed
If the user double clicks the row, the node expands/collapses

Did I get this right?

That is an option. A setting that lets me determine how many levels deep I want expanded by default would be SOOO much better since it would eliminate the need for double clicking!

A setting that lets me determine how many levels deep I want expanded by default would be SOOO much better since it would eliminate the need for double clicking!

While that might make sense in your use case I doubt it actually makes sense as a product setting. What value would you set it to? 2? 3? What if we decide to add/remove a level in that tree? It just doesn't make sense to me.
Not sure what we can do here.

A user defined setting means it is always the depth I want. I have two PHP parsers (since I have to develop with the horrid Code Igniter framework) so I have an additional depth that I assume a chunk of users wouldn't. If a numeric value doesn't make sense... What about an enum (I.e. namespace, class, function, variables)?
The point a setting is that the editor has what it thinks is the sensible default, but the use gets to choose when the default isn't "right", as far as they are concerned.

What I mean is that the correct value will always change, even for you. One day it will be X, the other day it will be Y. For the same workspace/folder/file/outline. It just doesn't sound feasible.

That is the nice part. Its a setting and could be changed. If structured properly I'm guessing this could be something that is language based.
If this is an enum value it would rarely (most likely never) change for me. If there is an internal discussion on this and it still doesn't seem feasible than the summary you provided previously would much better than the current implementation.
For some reason, it has been deleted, but there was a previous comment that seemed to echo the desire for more settings surrounding the code outline pane. It is an amazing tool, but at the moment the defaults cause some annoyance around it!

The recent changes in the default outline display has degraded it's usability.
Originally when opening a file the Outline would by default display the functions which was perfect, or the classes and functions. I'm always looking for a particular function in a file, and having them listed alphabetical is perfect. (I normally have only a single class per file so in general I only have a single list of functions for each file).
The current version however lists all functions constants and variables, this is really long as my files can be quite large (lots of functions). So I use the "collapse" button - this works in a file that only contains functions - the functions are all listed alphabetically. But in a class file the collapse function then shows all of the classes, and generally I only have one class per file, so it lists one class name. I then have to expand the class to see the functions. This is 2 clicks more than I want.
Can we please have the outline default to listing functions only? Or as Jared suggests, an option we can set indicating a default depth.

I'll leave his name out in case he has removed this for some specific reason but wanted the sentiment included in the issue.

Hi Jared
Having a configurable number of levels will not work.  We need more
intelligence than this.  For example:
A library of functions might contain just functions, so we only want this
expanded to 1 level:
function abc() {
}
function def() {
}
A class file might contain a class and functions, so we want this expanded
to 2 levels:
class xyz {
function x1() {
}
}
So, either the outline tool needs to be intelligent enough to determine the
difference between class names and function names, or, a level is used but
then remembered for each file name opened.
Cheers
Murray

@murraycollingwood I think you are placing too much on the outline piece itself. Just like with #region this could be up to the plugins for a language to implement. If an enum is used I'm having trouble seeing makes that problem something that couldn't be overcome?!

Closing this as idle. It's not very clear how well this could work and whether it would really improve usability. Sorry.

Closing this as idle. It's not very clear how well this could work and whether it would really improve usability. Sorry.

@joaomoreno You have us 2 minutes to close and then closed it yourself.
This problem still exists, and I think I have a better solution suggestion.
Instead of specify the number of levels to expand, perhaps we can specify the number of levels not to expand.  That is, in a tree analogy a value of -1 does not expand to the leaves, it only expands to the twigs.
Here is an image of what I currently get when opening a file:

Here is an image of what I want when opening a file:

Does that help explain?

Yes it definitely does. But it seems overly specific to the Outline view. Again, this is hard to generalize over other trees.

I'd agree with @murraycollingwood that initial state of the outline should be collapsed. While full expansion may be useful for very small classes, something bigger will be only usable through search/filter.
I also think that a click on the row should expand the outline too, if it's not yet expanded.

As I see it, the problem is that expand-all makes too many rows visible. Maybe a good heuristic could be based on not just the depth level, but also the number of visible rows.
A simple example would be to expand depth levels until no more than N rows are visible.
A more complicated example would be to expand to at least depth D, and then keep expanding until no more than N rows are visible.
I don't know whether this would actually feel good in practice, but using the number of visible rows in the heuristic might be worth a try.

/duplicate of https://github.com/microsoft/vscode/issues/53262


Add inferred component name(__name) to

What problem does this feature solve?
compiler-sfc adds __name property to <script setup>, but it does not adds __name property to regular <script>. Is it appropriate to add __name to all types of <script> so I can get inferred name if one component does not have a name property.
What does the proposed API look like?
In all conditions, I can get __name:
export default {
  mounted() {
    console.log(this.$options.__name)
  }
}

<script setup>
const inst = getCurrentInstance().proxy
onMounted(() => {
  console.log(inst.$options.name)
})
</script>

If you only need the component name, you can retrieve it using the following code within the setup function: getCurrentInstance().proxy.$options.name. When you use Single-File Components, the component already infers its own name from the filename.


remove override of struct toHash and opEquals in example.

The struct MyString example didn't compile because the methods were marked as override.

Oh... The redundant override keyword has been removed in #1106.


Fix #1 - Persistent 3D tracer waveforms

Some simple modifications to where and how often the background() is redrawn can fix the draw persistence behavior :smile_cat:
Not sure how to fix the blue color's brightness to behave like the original YouTube video.  That is to say: There is now no difference between the 3D "scan" line and the persisted drawn trails.

Thanks for the attempt. I'm hesitant to merge this as-is because it breaks the 3D camera movement, it feels very choppy and clears the existing geometry. Maybe we can find a different solution.

So the simpler 3D drawing technique I was using in 0d9e9dbd7d7aa55f6d241dee55f4af30711219d7 still works:

Maybe we just need to go back to basics and start over on the drawing code. I had a 3D mesh version of this that looked pretty cool but I'm not sure why it stopped drawing the faded lines.

This is the commit that appears to have broken the drawing code on processing 3:
https://github.com/fadookie/Super3dvisualizer/commit/372a9cc

Thanks for the attempt. I'm hesitant to merge this as-is because it breaks the 3D camera movement, it feels very choppy and clears the existing geometry. Maybe we can find a different solution.

Yeah, I'm a newbie at Processing 3 but it's the only solution I could figure out so far to get persistent waveforms.  It creates the problem of needing to clear the background on camera movement or perspective changes.  Not sure how this problem is solved usually.  The backroundRedrawFrameDivisor variable can be tweaked to try and adjust the choppiness.
There's probably a better way to do this.  I'm not sure how to persist drawn 3D objects, but maybe there is a way to do 3D transforms when changing camera perspective.  I'm not too familiar with the differences and 3D objects in Processing like TRIANGLE_STRIP vs. QUAD_STRIP.  I only just started with Processing 3 recently with the tutorial recently and it was showing the background() draw trick in 2D.
That screenshot looks pretty good! I like the lighting and shadows effect.  I was experimenting with using different blendMode toggles in the zPosition loop and got something that looked interesting:
diff --git a/Super3dvisualizer.pde b/Super3dvisualizer.pde
index c71aba7..311af14 100644
--- a/Super3dvisualizer.pde
+++ b/Super3dvisualizer.pde
@@ -37,6 +37,7 @@ float[][] geomBuffer;

 int mouseDraggedFrame = 0;
 static final int backroundRedrawFrameDivisor = 20;
+int blendModeToggle = 0; // initial blendMode(REPLACE)

 void setup()
 {
@@ -163,9 +164,22 @@ void draw()
   float redFactor = 30;
   float greenFactor = 0;
   float blueFactor = 200;
-
+
   for (int zPosition = bufferStart + 1; zPosition != bufferStart;) {

+    if (zPosition == bufferStart + 1) {
+      // Toggle blendMode on each pass to yield slightly different colors for:
+      // 1) 3D "scan" line
+      // 2) Persisted drawn 3D tracer trail
+      if (blendModeToggle == 0) {
+        blendMode(SCREEN);
+        blendModeToggle = 1;
+      }
+      else {
+        blendMode(REPLACE);
+        blendModeToggle = 0;
+      }
+    }
     //;pow(geomBuffer[i + 1][band], power) * -1
    //println(bufferStart + " " + zPosition);

This is the commit that appears to have broken the drawing code on processing 3:
372a9cc
The only big difference I see is I switched from TRIANGLE_STRIP to QUAD_STRIP - maybe the API for this changed subtly in 3.0? Could always go back to tri strips again.

Just looked at the diff for 372a9cc and saw something that gave me a hunch, (maybe it's just because I don't understand yet the use of shape functions well enough yet).  Does the order and placement of endShape() matter here with persistence of 3D shapes?  I see the TRIANGLE_STRIP has changed levels within the two nested loops.  Also, there's now two beginShape() calls:

beginShape(QUAD_STRIP);
beginShape(TRIANGLE_STRIP);

Do these need to have matching pairs of endShape() to go with them?  If so, I'm not sure how Processing would know which is which, maybe it's missing something?  How does the nesting level affect these shapes?

Yeah so check the docs for beginShape.  QUAD_STRIP is for specifying adjacent quads. It's possible something changed in the drawing code for Processing 3 where some previous drawing technique no longer works for some reason.

I'm not sure why I changed the loop structure there. But I remember at one point I was doing each part of the mesh as a strip of triangles and switched to those wireframe lines at that commit I linked earlier.
I'd say for now it's probably easiest to switch back to rendering a simpler type of mesh using triangle strip wireframes based on the working commit I linked above.

Alright I messed with this a bit today and was able to get it working by reverting back to a more normal technique for drawing triangle strips. I am going to close this PR since I think my solution works better with a moving camera. I also switched the camera to use PeasyCam which is hopefully a bit more user- and programmer-friendly. Thanks for giving me a kick in the but to get this fixed!


Randomize pivot value in implementation of quick sort algorithm,

Currently, the last element is always picked as the pivot. Randomize this such that the pivot is a random number between the "start" and "end" indices passed to the partition function.
Test your solution properly before opening a PR.

can i work on it?

@Mystigan Please review my PR and give me feedback.


[CI] Add more unit test to ensure the the outputs are reasonable

Description
Our unit test ensures that loading model and running inference successfully, but cannot indicate the output is reasonable instead of kinda garbage. Currently we need to run the examples when making some major features & fix, which is a bit annoying.
To address this issue, I think we could send the output to OpenAI chatgpt to check if it's reasonable. I will afford the payment of the tokens but will use github.triggering_actor to allow only developers who have write access to trigger the corresponding workflow.

We could also hardcode the expected responses in the unit tests. For example in this test it generates two completions of "Question. what is a cat?\nAnswer:" and assets that they are the same. We could assert the exact response too.
Of course this would only work with temp=0 and a specific model (even a specific quantisation), but it might save a few OpenAI calls!

In my opinion it would be easier the alternative that Martin proposes. We can not run all the test in CI y we should verify all the test locally.

We could also hardcode the expected responses in the unit tests.

Yes, I also want to save the tokens where this approach works! I'll only consider using OpenAI API when necessary.

We can not run all the test in CI. we should verify all the test locally.

I tend to view things a bit differently. The workflows and unit test are responsible for reducing the risk when we merge the PRs. As long as the workflows pass, it should be equal to saying that terrible behaviors won't appear if we merge the PR.
However, due to the GPU backends, it's indeed hard for us to cover all the cases in the workflows. I can provide a machine with Nvidia GPU and Linux OS to run the workflows, but no idea for Windows yet. :)


MRG: Fix dtype

Looks like back in 2012 I missed one:
https://github.com/mne-tools/mne-python/commit/b1634cd3a602643138161e37d83effd079a7a8ce
Ready for review/merge from my end. It wasn't caught by tests because we don't have any files that use it. I got a hold of a file that did (exported from xplotter I think?) but it's too big (13 MB) to justify adding.

thx @Eric89GXL


Sparql wrapper

As it was previously discussed in #33 -- main downside was SPARQLWrapper did not support content-type CSV. Since very recently it does, so we can use SPARQLWrapper.
There is one advantage: we can then provide SPARQL results in all their supported formats (HTML not supported, which we do at the moment, but that can be fixed).

Moving to new PR


pandoc: Unable to convert

Dear @benweet,
I just tried to export a document to PDF but received the following error:
pandoc: Unable to convert `/tmp/tex2pdf.96/5d424bc6132b73039c2e9740a900ba6606b4179a.shtml' for use w

The document contains some sensitive information. Therefore, I cannot share it unfortunately.
Any steps I can do to further debug the problem?
Thankfully,
~ Robert

Hi @orschiro
Can you try to localize the problem by removing parts of the file and eventually share only the paragraph that is causing the error?

@benweet
I identified the problem.
It was the following code:
![](https://photos-3.dropbox.com/t/2/AAC6acqUywa1KqYUWovVjFeaCepN-BcUPESgs40KtzjTLQ/12/8902804/png/32x32/1/_/1/2/Signature.png/EJix0AYY8Z4NIAcoBw/idusCMemHpOcDRptplGUTPEmdYK3ninaYXKm0StcFGA?size=1024x768&size_mode=3)

Is it possible for Classeur to support local image paths?
For example, I don't want my signature image to be uploaded onto Imgur but prefer to reference it locally.

You could use data uri:
![red dot](data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAUAAAAFCAYAAACNbyblAAAAHElEQVQI12P4//8/w38GIAXDIBKE0DHxgljNBAAO9TXL0Y4OHwAAAABJRU5ErkJggg==)

Can the data uri reference to a local file?
If not, then it doesn't solve the problem of sensitive images not being hosted on public file hosting, I'm afraid.

Data uri is self-contained (the whole image data is contained in the uri in base64). So the image will be hosted by the markdown file itself (eventually it will be saved on Classeur servers, but not accessible publicly).
Hope it helps.

It works! Thanks for your help.
I used duri.me to convert the image into base64 code.
The only downside is that the pasted code is very long and takes up a lot of space in the document.

Closing this one as I don't see any way for pandoc to access private external images.

Thanks for bringing this to an end!
The URI method works well enough and should maybe added to the documentation for private-sensitive users.
~ Robert


Optimize and Cythonize MGC

Pull Request Test Coverage Report for Build 95

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at ?%

Totals

Change from base Build 89:
0.0%

Covered Lines:

Relevant Lines:
0

💛  - Coveralls

Need to make sure, that the Cython code is covered by pytest. It is covering, but not reporting it. Will fix it in another PR.


Initial setup for guides

Create Guides/ top-level dir
Move README "creating first list" contents into Guides/Getting Started.md
Add initial Guides/Migration.md (ref #221)
Fix #245

See rendered guides at:

https://github.com/Instagram/IGListKit/blob/guides-setup/Guides/Getting Started.md
https://github.com/Instagram/IGListKit/blob/guides-setup/Guides/Migration.md

Preview of generated docs:

I haven't re-gen'd the docs yet -- so that this is easy to review.
Before merging, I'll re-gen docs and merge everything at once.

Ok -- went ahead and re-gen'd the docs.
To review, just look at the first 2 commits. 😄

Coverage remained the same at 94.481% when pulling 8d9c7ac535157f1f55e592c9e8df2973da3c221d on guides-setup into 90cf9d5dfba5151c9c9601b9b8fb4afae3bbefb9 on master.