-
Notifications
You must be signed in to change notification settings - Fork 456
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
Clear out-of-date files in global storage #2597
Comments
I remember @rgrunber mentioned this before: #2285 (comment) We have already updated to M2E 2.0, so is there any difference on size of the recent versions? Besides, we can have such logic to clean previous global storage folders. |
Yes the size is smaller. For example, the size if the folder |
As per discussions, maybe there is some feature to have VS Code clear such cached folders at the platform level ? Or maybe there is something we can take advantage of in VS Code API that can mark those folders for deletion on certain staleness criteria ? |
Signed-off-by: logonoff <[email protected]>
Signed-off-by: logonoff <[email protected]>
Signed-off-by: logonoff <[email protected]>
Signed-off-by: logonoff <[email protected]>
Signed-off-by: logonoff <[email protected]>
The extension will store some caches in global storage with each version. Each version will occupy around 15~20MB, which the total size will be quite large when users switched to the pre-release channel.
We can consider detect the out-of-date version and remove it.
The text was updated successfully, but these errors were encountered: