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

Problem upgrading to 2.2.3 #1017

Open
ybertot opened this issue Jan 29, 2025 · 2 comments
Open

Problem upgrading to 2.2.3 #1017

ybertot opened this issue Jan 29, 2025 · 2 comments

Comments

@ybertot
Copy link

ybertot commented Jan 29, 2025

On one of my computers, I am using vscoq 2.2.3 and it works fine.

On another computer, I was still on vscoq 2.2.1 so I decided to upgrade. I started by upgrading the opam package for vscoq-language-server, and then clicked on the extensions icon and required for the upgrade of vscoq.

When I click on the button : "update to v2.2.3"

025-01-29 11:00:58.205 [error] invalid central directory file header signature: 0x0: Extract: invalid central directory file header signature: 0x0
at V.extractUserExtension (/usr/share/code/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:102:111355)
at async ie.u (/usr/share/code/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:102:117590)
at async ie.x (/usr/share/code/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:102:119507)
at async ie.h (/usr/share/code/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:102:117123)

After investigating the issue, it appears that the error message correspond to some zip file being corrupted. I tried deactivating the extension completely (uninstall) and then redoing the install, but there is not much progress.

@ybertot
Copy link
Author

ybertot commented Jan 29, 2025

It finally got fixed after I performed the following two operations:

  • I removed all files of the form .[0-9a-f]* in directory $HOME/.config/Code/CachedExtensionVSIXs/ (I thought about looking in that directory because some of the messages I had in the output console of Visual Studio code mentioned system errors while accessing files there, but I lost these error messages).
  • I asked for the vscoq package to be complete uninstalled and re-installed

I did not succeed on the first uninstall - install loop, though. I also had to restart the Visual Studio code progress several times. Maybe there is a specif order in which all these operations must be performed.

@ybertot
Copy link
Author

ybertot commented Jan 29, 2025

Maybe this should not be recorded as an issue, but the information may be worth adding in a "troubleshooting" section, when we understand it better.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant