Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Files are not closed in workspace service in Linux #1901

Closed
3 tasks done
fflaten opened this issue Aug 18, 2022 · 1 comment · Fixed by #1902
Closed
3 tasks done

Files are not closed in workspace service in Linux #1901

fflaten opened this issue Aug 18, 2022 · 1 comment · Fixed by #1902

Comments

@fflaten
Copy link
Contributor

fflaten commented Aug 18, 2022

Prerequisites

  • Write a descriptive title.
  • Make sure you are able to repro it on the latest version
  • Search the existing issues.

Steps to reproduce

  1. Open a new instance of VSCode on Linux
  2. Open a file
  3. Test symbol search. It will show symbols in file
  4. Close file
  5. Test symbol search again.

They will still be there even though workspace symbols (search) should only track open files

Expected behavior

File will be closed -> no symbols shown in symbol search

Actual behavior

Files are added on open, but never closed. -> symbol search shows values for every file opened or scanned at some point

Error details

No response

Environment data

Name                           Value
----                           -----
PSVersion                      7.2.3
PSEdition                      Core
GitCommitId                    7.2.3
OS                             Linux 5.10.102.1-microsoft-standard-WSL2 #1 SMP Wed Mar 2 00:30:59 UTC 2022
Platform                       Unix
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Version

2022.8.2 preview

Visuals

No response

@ghost ghost added the Needs: Triage Maintainer attention needed! label Aug 18, 2022
@fflaten
Copy link
Contributor Author

fflaten commented Aug 18, 2022

This is caused by a casing mismatch in keys. Files are added to workspaceFiles using real path on linux, but removed using ScriptFile.Id which is always FilePath.ToLower().

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants