-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Anyway to automatically upgrade VSCodium with system setup on Windows? #411
Comments
Well, you can automate that too :) Sorry, I just discovered this project moments ago. So, hi. |
Auto updates should work out of the box. We run a small server (https://GitHub.com/VSCodium/update-api) that VSCodium calls to check for the latest release on GitHub. Have you noticed that updates are not working? If so can you provide some more context about what version, OS, etc you're running? |
It's greate. |
@Lierrmm can you provide OS + arch + type of installation (archive, system, user)? I just poked the API with the various combinations and look good. I suspect MS may have changed the way in which they call the Update API for some specific combination. https://vscodium.now.sh/api/update/win32-x64-system/stable/asdf |
win32-x64-system was the version of VSCodium I installed. System Details from winver: Windows 10 Pro 1909 Build: 18363.836 |
Based on this code snippet, I think the issue is that MS is no longer sending "-system" up for x64 system install. As far as I can tell (pls check my work!), the platform combinations should hit the following urls (asdf is the "commit" portion of the url):
The fix should be fairly trivial change in https://github.com/VSCodium/update-api (PRs welcome; I'll work on it if I have a free hour to focus). |
Just a related note- auto-updates via package managers (of this and a multitude of other software) is a general option, too (works fine for me on Trisquel GNU/Linux, should work fine on other systems, too as long as you use the available package managers - see https://vscodium.com/#install). |
From 1.45.1 to 1.46.0, it seems working, it shows downloading in the menu. |
Didn't work for me with:
Still getting a 404 error. @playgithub Does it work for you? Do you also use a x64 version? |
It shows downloading as Menu/Help/Dowloading Update...
|
Rechecked, that is what my log says:
Is there a way to log more details? |
|
@playgithub Do you have a 32bit or 64bit version of VSCodium? [if not100% sure: open it, open it, then open taskmanager->details, right click on the columns, choose "platform" and have a look] |
x86 64bit |
With a proxy, successfully updated from 1.46.0 to 1.46.1 |
So do the people that get a 404 need to configure a proxy? If yes how? |
On Windows, shadowsocks client will set the proxy in system level automatically, vscodium use that automatically. |
I believe the problem is still with @playgithub Update does work in a
|
@stripedpajamas I wonder if you have time to take a look at VSCodium/update-api#5, see whether it meets #411 (comment). |
So I've searched for hours now if it was my pihole or nextdns filter but it seems not. I still have 404 error. |
@boistordu The current state is "works with user setup, doesn't with system setup". |
of cause, edited |
Thanks to @Heptazhou for the PR; https://vscodium.now.sh/api/update/win32-x64/stable/asdf now returns an update blob. Can the people who have Windows x64 system setup see if the auto update is working? If you've already updated to latest version, you at least shouldn't get a 404 anymore. The responses from the update API for valid inputs are 200 (update available), and 201 (no update available). |
Now I have to check github periodically to see if there is a new version.
The text was updated successfully, but these errors were encountered: