No way to disable either move logs

[irvnriir]

Prerequisites

• I have written a descriptive issue title.
• I have searched all open and closed issues to ensure it has not already been reported.
• I have read the troubleshooting guide.
• I am sure this issue is with the extension itself and does not reproduce in a standalone PowerShell instance.
• I have verified that I am using the latest version of Visual Studio Code and the PowerShell extension.
• If this is a security issue, I have read the security issue reporting guidance.

Summary

even "powershell.developer.editorServicesLogLevel": doesn't have a full disable option .

sometimes, for security, logs is required to not be kept in folders with executable files ,

i also periodically get this notification

i did the comparison, the only extension that gets modified is ms-vscode.powershell-<<..>> .

PowerShell Version

Name                           Value
----                           -----
PSVersion                      5.1.19041.1320
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}

Visual Studio Code Version

1.68.1
30d9c6cd9483b2cc586687151bcbcd635f373630
x64

Extension Version

[email protected]

Steps to Reproduce

get syntax errors in Powershell files

Visuals

No response

Logs

No response

[andyleejordan]

@irvnriir have you been able to test this in the preview?

[ghost]

This issue has been marked as fixed. It has been automatically closed for housekeeping purposes.

[irvnriir]

@andschwa nothing changed

[andyleejordan]

@irvnriir did you clean that directory up, and can you test the new None option?

[andyleejordan]

You have to have a workspace open for the workspace storage directory to be available for saving logs there.

[irvnriir]

@andschwa there is no none option . one present in powershell.pester.debugOutputVerbosity , but not powershell.developer.editorServicesLogLevel .

[irvnriir]

check whether the version at screenshot (the only available) is the one including the update .

[andyleejordan]

😬 I thought I'd included it in the last preview, it was not. I'll ping you when the next one is out 😅

[andyleejordan]

Hey @irvnriir I just released v2022.7.1-preview, with this fix! Can you test it out and verify for me? Let me know if you find anything else being written to the extension installation directory instead of the workspace storage!

[irvnriir]

seems working . though its very wrong that it saves logs to Workspace Storage and not globalStorage .

how you expect logs that are no longer relevant be cleared ?

[andyleejordan]

...I swear I was pointed at workspace storage as the correct place to put them. Moving to global storage.

how you expect logs that are no longer relevant be cleared ?

IDK, what's the current behavior?

[irvnriir]

well, i didn't point there, i pointed "userfiles" -- (global) .

IDK, what's the current behavior?

(the issue appears if you choose the W. Storage)

[andyleejordan]

I'm sorry, I don't understand your reply. Can you try again?

[irvnriir]

leave it, all s fine since

Moving to global storage.