Extension incomplete after update

[egamma]

pls see this issue https://github.com/Microsoft/vscode-tslint/issues/324.

[egamma]

Another instance of a corrupt extension https://github.com/Microsoft/vscode-tslint/issues/323#issuecomment-366261023.

I´m starting to think that we should have a checksum for an installed extension so that we can detect a corruption and recover from it.

[thorn0]

@egamma wrote:

One more thing can you please attach the log for the shared process to #43813?

Here you are: shared.log

[sandy081]

@thorn0 From the logs I am guessing following:

• You have deleted TS Lint extension from the disk
• You installed TS Lint extension again freshly

After this, I think you have TS Lint extension working.

I would be interested to know how the extension got corrupted before above happened. We preserve logs for last 10 VS Code sessions, hoping that the corrupted extension might occurred during those 10 sessions. Can you please share the logs of the shared process from last available sessions. To get that

• Open logs folder. Use command Open Logs Folder. This will open the logs folder for current session.
• Go to its parent folder where you can see all sessions and you can get the logs of shared process from there.

Also, any idea if you restarted (quit and restart) VS Code while the update of TS Lint extension is happening?

[thorn0]

That's what helped:

1. I have uninstalled the extension
2. But the corrupted folder still was there, so I deleted it myself
3. I installed TS Lint extension again freshly

First I tried reinstalling the extension without the step 2, but it didn't help.

We preserve logs for last 10 VS Code sessions

Sorry, I open and close VS Code often enough, so there are only today's and yesterday's logs there.

any idea if you restarted (quit and restart) VS Code while the update of TS Lint extension is happening?

Probably. Extensions are updated automatically, so I don't pay much attention to their updating.
Also I had this issue: #43503

[sandy081]

Logs at the point of the corruption would have been helpful to know what happened. My suspect is that code would have been restarted while extension update is in progress.

[vscodebot]

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.

Happy Coding!