Closed secondl1ght closed 4 months ago
Yup. Happens here too, and just in the last version "1.86.2" In the previous version "1.85.2" it don't happen.
Going a little deeper into this, I discovered that the error is about the TS extension not founding this file here: "/usr/share/codium/resources/app/extensions/node_modules/typescript/lib/typescript.js". In fact, the 1.86.2 don't even have the "node_modules" folder, so it can't find the typescript stuff.
Hope it helps you guys to solve this problem!
oh!
I will have to check it...
I'm pretty sure it's due to that line: https://github.com/VSCodium/vscodium/blob/f309a13e49054b50e3b7270cbd10987c51584cd0/.github/workflows/stable-linux.yml#L110
(done so we can support glibc2.17
)
@daiyam if you need someone to test, just let me know.
@ToMattBan will do
Same issue O.S : Kali Rolling Version: 2024.1 @daiyam Great Software
Hello @daiyam, i've got the same error after updating VSCodium 1.85.2 to 1.86.2 OS: Ubuntu 22.04.4 LTS Thanks for your work frérot.
edit :
I have also a Volar (Vue) extention installed and it try to find out typescript.js file but can't.
[Error - 22:49:51] Server initialization failed. Message: Request initialize failed with message: Can't find typescript.js or tsserverlibrary.js in /usr/share/codium/resources/app/extensions/node_modules/typescript/lib Code: -32603
I think that it will affect any extention that depends on this file.
I'm having the same issue on v1.86.2.
@ToMattBan and others, a test version is available at https://github.com/VSCodium/vscodium/actions/runs/8012468841 (in the artifact bin-x64) First of all, do you have access? Can you test it? Thx
And, for me, the typescript service is now correctly working.
Same error for me, downgrading made the job for now.
@daiyam I was able to access the test version. I tested the AppImage from the bin-x64 artifact and it works fine :+1:
1.86.2.24054 is out and fix the issue.
Amazing, Thanks very much
Works fine now. Thanks so much for your reactivity @daiyam, you the best !
Thank you @daiyam . The new version works like a charm! I tested with some extensions that were bugging but now everything are working as expected!
Thank you @daiyam. How long does this usually take to enter the debs repository?
to enter the debs repository
What do you mean?
to enter the debs repository
What do you mean?
This: https://gitlab.com/paulcarroty/vscodium-deb-rpm-repo
I currently cannot downgrade using it, so I will have to wait until it is updated. It’s not an issue, per se, so I thought it might be okay to ask here in this thread.
@bitstein I just installed using the deb in the release section for now. It should update itself when launching new versions. No need to wait to install from the deb repos
@ToMattBan No, on Linux, the automatic updates are disable due to some users clicking on the update (which resulted to other issues) when they should use the app manager. I've also assumed that those who are using the .deb, known how to update it themself.
@daiyam Sorry, I build my sentence wrong. Didn't mean automatic update, but automatic search for updates. At least here, when I downgraded I got a update request in my update manager.
to enter the debs repository
What do you mean?
This: https://gitlab.com/paulcarroty/vscodium-deb-rpm-repo
I currently cannot downgrade using it, so I will have to wait until it is updated. It’s not an issue, per se, so I thought it might be okay to ask here in this thread.
i guess we'll have to wait ....
Sorry, I didn't understand the issue.
There is the error when building the repo: ERROR: Uploading artifacts as "archive" to coordinator... 413 Payload Too Large id=6239193797 responseStatus=413 Payload Too Large status=413 token=glcbt-65
@paulcarroty, maybe the Insiders version isn't needed in the repo? What do you think?
It has been fixed.
For reference: https://gitlab.com/paulcarroty/vscodium-deb-rpm-repo/-/issues/98
Thank you!
Describe the bug After just updating VSCodium I opened the application and got the following error:
Please confirm that this problem is VSCodium-specific
Please confirm that the issue/resolution isn't already documented
To Reproduce Steps to reproduce the behavior:
Expected behavior No error.
Screenshots![image](https://github.com/VSCodium/vscodium/assets/85003930/63689b19-7639-4641-a71d-ee14100286b6)
Desktop (please complete the following information):
Additional context Thanks