Syntax checker not detecting change of files.

[jhoneill]

Prerequisites

• I have written a descriptive issue title.
• I have searched all 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

I can not see this as an issue and I think it is the extension but it may be VS code itself (if so I'll close this and and open there).

I'm working with some scripts which generate other PowerShell scripts, so the process goes

• Edit generator or Edit instructions in VSCode
• Run the generator script from the PowerShell integrated console
• Edit the resulting code

What I'm finding is the error highlighting is marking thing in the text as errors which were in a previous version. What seems to cause this is the change made to the file outside VS code, as if there is a copy cached, which is still used when the updated file is opened.

PowerShell Version

Name                           Value�[0m
----                           -----�[0m
PSVersion                      7.2.4
PSEdition                      Core
GitCommitId                    7.2.4
OS                             Microsoft Windows 10.0.19042
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Visual Studio Code Version

1.67.2
c3511e6c69bb39013c4a4b7b9566ec1ca73fc4d5
x64

Extension Version

[email protected]

Steps to Reproduce

1. Add extra lines containing a syntax error to an otherwise valid file. Problems should be displayed correctly
2. Close it, and edit it outside VS Code to remove the error
3. Reopen in VSCode and note the problems show before are still show. (see Visuals below)

Visuals

Logs

No response

[jhoneill]

Postscript - this also seems to impact folding. If the file has changed in the middle folding tries to fold were the old file should have folded.

[SydneyhSmith]

@jhoneill thanks for the issue report...if you edit the open file at all in VSCode, does this problem go away?

[jhoneill]

No - not quite.
I opened the file in notepad and vscode.
I made a couple of breaking edits an extra } at the end and unused variable , saved & closed, in Code, and then saved from notepad to back out out the changes.
If I add and delete spaces at the end, it stops complaining about the extra } but nothing seems to get rid of the complaint about the unused variable, and folding is off by one line as if the extra variable line is still there.

[jhoneill]

And if I close and re-open the file it adds an extra instance of the erroneous message each time

[andyleejordan]

@jhoneill the latter is sadly known: #3252

[ghost]

This issue was closed automatically as repro info was indicated as needed, but there has been no activity in over a week. Please feel free to reopen with any available information!

[jhoneill]

@SydneyhSmith the bot shouldn't have closed this - do you need any more repro info ?

[SydneyhSmith]

Thanks, reopening

[SydneyhSmith]

Thanks @jhoneill we discussed today and we believe fixing #3252 will resolve both issues, so we will link the issues and mark this as a duplicate for now...thanks!

[jhoneill]

@SydneyhSmith If both get fixed together that will be great.

[ghost]

This issue has been marked as duplicate and has not had any activity in a day. It has been closed for housekeeping purposes.