Vscodium: Connections to marketplace

[daniel-molina]

Describe the bug
I went to Network and I saw that vscodium is connecting to

https://marketplace.visualstudio.com/_apis/public/gallery/extensionquery

Reading Docs page I learned about product.json which is said to be set to open-vsx.org. I checked /usr/share/codium/resources/app/product.json and I found that

"extensionsGallery": {
"serviceUrl": "https://marketplace.visualstudio.com/_apis/public/gallery",
"cacheUrl": "https://vscode.blob.core.windows.net/gallery/index",
"itemUrl": "https://marketplace.visualstudio.com/items"
},

It does not seem that way.

Please confirm that this problem is VSCodium-specific

• [ ] This bug doesn't happen if I use Microsoft's Visual Studio Code. It only happens in VSCodium.

I do not use vscode, so i do not know.

Please confirm that the issue/resolution isn't already documented

• [X] I checked the Docs page and my issue is not mentioned there.

To Reproduce
Steps to reproduce the behavior:

Browsing or installing extensions.

Expected behavior
No connections to Microsoft MarketPlace.

Desktop (please complete the following information):

• OS: Debian-based.
• Architecture: x64
• Version: 1.45.1

[stripedpajamas]

Open VSX marketplace is available in v1.46.0 and higher.

[GammaGames]

I'm not sure if this issue is related to codium or openvsx or if I should open a new issue, but I can't find any extensions when I search.

I looked at the request that's being sent, the payload is:

{
  "filters": [
    {
      "criteria": [
        {
          "filterType": 8,
          "value": "Microsoft.VisualStudio.Code"
        },
        {
          "filterType": 10,
          "value": "test"
        },
        {
          "filterType": 12,
          "value": "4096"
        }
      ],
      "pageNumber": 1,
      "pageSize": 50,
      "sortBy": 0,
      "sortOrder": 0
    }
  ],
  "assetTypes": [],
  "flags": 946
}

And I get a 500 response of:

{
  "timestamp": "2020-06-12T15:33:26.792+0000",
  "status": 500,
  "error": "Internal Server Error",
  "message": "sortOrder parameter must be either 'asc' or 'desc'.",
  "path": "/vscode/gallery/extensionquery"
}

[stripedpajamas]

That looks like an open vsx bug to me. Can you open an issue at https://github.com/eclipse/openvsx/issues and link it to this one?

[stripedpajamas]

I will reopen this in case anyone else is having the same issue connecting to open vsx.

[stripedpajamas]

cc @spoenemann

[aniketbarik]

I'm facing this same issue.

VSCodium details -

Version: 1.46.0
Commit: a5d1cc28bb5da32ec67e86cc50f84c67cc690321
Date: 2020-06-11T18:31:22.701Z
Electron: 7.3.1
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Linux x64 5.6.16-300.fc32.x86_64

[lion24]

Hi all,

I'm also impacted by this issue.

codium build:

Version: 1.46.0
Commit: a5d1cc28bb5da32ec67e86cc50f84c67cc690321
Date: 2020-06-11T18:31:22.701Z
Electron: 7.3.1
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Linux x64 5.5.15-200.fc31.x86_64

[lalincedeldeserto]

Hi!
I'm having the same issue:

Version: 1.46.0
Commit: a5d1cc28bb5da32ec67e86cc50f84c67cc690321
Date: 2020-06-11T18:31:22.701Z
Electron: 7.3.1
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Linux x64 5.4.0-7634-generic

[ghost]

I tried to delete config files for a full reset and the problem still persists.

[GammaGames]

FYI since this was a comment on #415, the docs have a method to revert back to the VS Code Marketplace. I have done this temporarily until the issue (eclipse/openvsx/issues/126) is addressed.

[VadinV]

Hi, i'm having the same issue:

Versión: 1.46.0 (user setup)
Confirmación: a5d1cc28bb5da32ec67e86cc50f84c67cc690321
Fecha: 2020-06-12T10:32:02.515Z
Electron: 7.3.1
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
Sistema Operativo: Windows_NT x64 10.0.19041

[ghost]

@GammaGames any idea where to place product.json on my filesystem for MacOS? I ran

sudo find / -name product.json

and it came back with nothing.

EDIT: Just found it:

/Applications/VSCodium.app/Contents/Resources/app/product.json

[talentlessguy]

Same problem:

Version: 1.46.0
Commit: a5d1cc28bb5da32ec67e86cc50f84c67cc690321
Date: 2020-06-11T18:31:22.701Z
Electron: 7.3.1
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Linux x64 5.4.43-1-MANJARO

[phd]

Quick workaround:

Edit /usr/share/codium/resources/app/product.json:

Replace:

  "extensionsGallery": {
    "serviceUrl": "https://open-vsx.org/vscode/gallery",
    "itemUrl": "https://open-vsx.org/vscode/item"
  },

with:

  "extensionsGallery": {
    "serviceUrl": "https://marketplace.visualstudio.com/_apis/public/gallery",
    "cacheUrl": "https://vscode.blob.core.windows.net/gallery/index",
    "itemUrl": "https://marketplace.visualstudio.com/items"
  },

[talentlessguy]

@phd I don't have such folder... I installed VSCodium with AppImage :thinking:

[rauldipeas]

Thank you so much @phd! It's working now!

[bencrbcp]

@phd Life saver!

[ghost]

Why did we switch to open-vsx then? To go back to Microsoft's marketplace?

[Daniyal-Javani]

Also we have no access to open-vsx because of Iran sanctions but Microsoft's marketplace is working

[ghost]

@Rowisi Good question, but probably because the licensing restrictions to Microsoft's marketplace needs more investigation.

I'm wondering if we could add a feature to VSCode to be able to choose the Marketplace from the UI. I think that would be handy.

[joseluisq]

Same issue using VSCodium v1.46.0 on ArchLinux.

Temporary workaround:
Update product.json file following @phd's comment: https://github.com/VSCodium/vscodium/issues/418#issuecomment-643664182

File: /usr/share/vscodium-bin/resources/app/product.json

[wattry]

I upgraded to 1.46 and the market place stopped working. The console is showing 500 errors:

Request URL: https://open-vsx.org/vscode/gallery/extensionquery
Request Method: POST
Status Code: 500 
Remote Address: 34.98.99.180:443
Referrer Policy: no-referrer-when-downgrade
access-control-allow-origin: *
alt-svc: clear
cache-control: no-cache, no-store, max-age=0, must-revalidate
content-type: application/json; api-version=3.0-preview.1
date: Mon, 15 Jun 2020 01:05:33 GMT
expires: 0
pragma: no-cache
status: 500
strict-transport-security: max-age=31536000 ; includeSubDomains
vary: Origin
vary: Access-Control-Request-Method
vary: Access-Control-Request-Headers
via: 1.1 google
x-content-type-options: nosniff
x-frame-options: DENY
x-xss-protection: 1; mode=block
:authority: open-vsx.org
:method: POST
:path: /vscode/gallery/extensionquery
:scheme: https
accept: application/json;api-version=3.0-preview.1
accept-encoding: gzip, deflate, br
accept-language: en-US
content-length: 231
content-type: application/json
origin: file://
sec-fetch-mode: cors
sec-fetch-site: cross-site
user-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) VSCodium/1.46.0 Chrome/78.0.3904.130 Electron/7.3.1 Safari/537.36
x-market-client-id: VSCode 1.46.0
x-market-user-id: 5993b4fd-c0fb-411e-9f83-5da24e234b98
{filters: [{,…}], assetTypes: [], flags: 946}
assetTypes: []
filters: [{,…}]
flags: 946

I was using brew to manage VSCodium however I cannot select the previous version (1.45) so I manually reverted using the binary provided here and the market place started working again.

[ebell451]

@09wattry use the workaround provided by @phd here https://github.com/VSCodium/vscodium/issues/418#issuecomment-643664182

[wattry]

@09wattry use the workaround provided by @phd here #418 (comment)

@ebell451 This does not work on my system

[ebell451]

@09wattry the key is to find product.json and modify that file accordingly. On macOS, the location of the file is /Applications/VSCodium.app/Contents/Resources/app/product.json

[spoenemann]

I'm sorry for the inconvenience caused by this outage. We introduced a new sorting feature last week and forgot to test the vscode API adapter. Using https://open-vsx.org as marketplace for VSCodium works again now.

[lion24]

@spoenemann Hi ! I confirm it's working again :D

Thank you very much :)

[joseluisq]

Confirmed It works!
I think this issue can be closed now.

[NickKaramoff]

While I totally like the idea of moving away from Microsoft's marketplace to a community-managed one, the change was just too sudden. I normally don't expect to update the app as usual (a minor version bump, mind you) to see my extensions stop working and the marketplace switch to one with _266 extensions_. And the only way to switch back is to edit a file buried deep inside the program? Thank you, I guess?

[RaviKavaiya]

@NickKaramoff I agree...

[t-fritsch]

I totally agree with @NickKaramoff comment.

The idea is really great, but it should not be the default for updates of existing vscodium installs, or at least there should be :

1. a warning or any way for the users to actually know that it happened. I just found out this issue after hitting my head agains the wall (yeah, it really hurts ;) ) trying to understand why I couldn't find any of the extensions I usually find on marketplace.
2. an easy way to chose one or another marketplace and to make the switch. Open-vsx is great but as already said 266 extensions vs 18.918 leaves a lot of needs uncovered

Anyway, thanks a lot for the great work that is being done with VSCodium !

[spoenemann]

I understand that this move feels like a degradation of functionality, and I agree it should have been communicated in more ways than the README. But I think there is not really a choice. The Microsoft Marketplace Terms of Use allow to use it only "with Visual Studio Products and Services", which does not cover VSCodium as I understand it. Of course everyone can still decide to use it at their own risk. What about an extension that allows to switch marketplace with a command?

[joseluisq]

What about an extension that allows to switch marketplace with a command?

It can be fine as third-party extension (even this can be not compatible under MS Terms).
However I don't think is the way to do it on the scope of this project. As @spoenemann has pointed out.

1. Use Rights

b. Visual Studio Products and Services. Your right to use any underlying Visual Studio Products and Services will be governed by the agreement under which you purchased such products or services, and will be subject to the payment of fees for such products or services, where applicable. Marketplace Offerings are intended for use only with Visual Studio Products and Services and you may only install and use Marketplace Offerings with Visual Studio Products and Services.
— Microsoft Marketplace Terms of Use

For example, if someone wants to use the MS Marketplace, can choose VSCode rather than VSCodium.

Thoughts?

[ghost]

For example, if someone wants to use the MS Marketplace, can choose VSCode rather than VSCodium.

Yes, I thought the whole point of VSCodium was to escape Microsoft's legal jurisdiction. Not being able to use their marketplace is a bummer but is vital to ensuring that the mission of VSCodium is seen through.

[daniel-molina]

I suggest to collaborate porting packages that you find useful to open-vsx so at the end there are no big differences between both repositories.

[t-fritsch]

For example, if someone wants to use the MS Marketplace, can choose VSCode rather than VSCodium.

@joseluisq when there is such a gap, this is not really a matter of choice. Vscode (and VSCodium until then) became popular also because of the huge amount of extensions available. Not being able to install some popular extensions is a big pain for those (as me) who are trying to spread the good word of using vscodium in replacement of vscode (I'm a trainer and teacher and make every student I teach install VSCodium in every course I do since almost 1 year).

I agree that we all should try to make extension authors publish their work on open-vsx (who doesn't agree with that ?) but until the switch is made by a significant number of extensions, the situation is still quite messy. Saying that when someone isn't happy with open-vsx catalog, then he simply should use vscode, is quite deceiving and not helping vscodium to spread in my opinion.

I don't know if the threat of Microsoft terms is really a big problem since VSCodium is around since a lot of time and (correct me if I'm wrong) never been threatened by MS (I can't imagine MS sending their lawyers on VSCodium when at the same time they invest more and more on "open source community", but maybe I'm wrong). Leaving the option for every user to use one or another store without the need to struggle with a hidden product.json file would be really great.

[joseluisq]

@joseluisq when there is such a gap, this is not really a matter of choice. Vscode (and VSCodium until then) became popular also because of the huge amount of extensions available. Not being able to install some popular extensions is a big pain for those (as me) who are trying to spread the good word of using vscodium in replacement of vscode (I'm a trainer and teacher and make every student I teach install VSCodium in every course I do since almost 1 year).

@t-fritsch I think you misunderstood my point of view. I will be more clear.

I have wrote:

For example, if someone wants to use the MS Marketplace, can choose VSCode rather than VSCodium.

I have used the terms for example, meaning everyone is free to used what one prefer.
So No, it's not just a matter of choice what was disused here.
The point here is not the fact that community can push new extensions they want to open-vsx (nothing stop you to do it). Instead, the concern is the Microsoft Marketplace Terms of Use which is one of the reasons because I prefer to use VSCodium as well as telemetry-free. Of course you have your reasons because you use one or another.

Vscode (and VSCodium until then) became popular also because of the huge amount of extensions available.

That's not really true, it depends. For example in my case I use around 10 plugins or less in combination with IDE's for other purposes. Even until "the connection problem" to MS Marketplace already described here, I have realized about it because of the change to open-vsx when I wanted to upgrade some plugin that was ("unfortunately") pointing to MS Marketplace.

I agree that we all should try to make extension authors publish their work on open-vsx (who doesn't agree with that ?) but until the switch is made by a significant number of extensions, the situation is still quite messy. Saying that when someone isn't happy with open-vsx catalog, then he simply should use vscode, is quite deceiving and not helping vscodium to spread in my opinion.

It's your point of view. But I have clarified this above. Essentially you are free to choose what tool feel suitable for you, meaning you can even continue using VSCodium and if something is missing, you are free to contribute to continue supporting the project. That's how Open Source works.

I don't know if the threat of Microsoft terms is really a big problem since VSCodium is around since a lot of time and (correct me if I'm wrong) never been threatened by MS (I can't imagine MS sending their lawyers on VSCodium when at the same time they invest more and more on "open source community", but maybe I'm wrong).

Again, it's your point of view. I have not the same thinking about this.
As complement just take a look at this:

VSCodium:

• This is not a fork. This is a repository of scripts to automatically build Microsoft's vscode repository into freely-licensed binaries with a community-driven default configuration.
• binary releases of VS Code without MS branding/telemetry/licensing

I'm not a lawyer but meaning freely-licensed binaries as well as without MS branding/telemetry/licensing It makes incompatible MS Terms with this and open-vsx projects. Please correct me if I'm wrong. However VSCodium core and open-vsx maintainers can manifest their opinions to make more clear the aims of these project.

Leaving the option for every user to use one or another store without the need to struggle with a hidden product.json file would be really great.

Sure, that's what I have referred above. So feel free to contribute.
For example, an extension to switch between MS Marketplace and open-vsx APIs coming from community can not be a big deal. However have in mind the previous comments about MS Terms and related as well as the core motivations because this project was made possible.

Looking forward.

[t-fritsch]

Hello @joseluisq

I appreciate you took the time to reply and explain your point of view in detail. Thanks a lot ! I really don't agree with some points you mentioned but I think everything has been said.

I simply hope this kind of lacks in vscodium won't hurt his adoption.
I began to ask extensions authors to migrate but I'm sure a minority will do so (there are great extensions and themes out there that are unfortunately not heavily maintained).
Anyway, I'll try to adapt my courses to explain the way to install missing extensions (not sure to be able to convince existing vscode users to do the switch with such workflow, but who knows...)

Best regards

[joseluisq]

Anyway, I'll try to adapt my courses to explain the way to install missing extensions (not sure to be able to convince existing vscode users to do the switch with such workflow, but who knows...)

In that case an extension that addresses that missing feature can be fine. Maybe with some indication to users explaining the Ms terms, etc.

I don't want to discourage VSCodium community usage. In fact VSCodium is my default editor personal and work use. My intention was to try to help people here to differentiate a bit better between both projects and transmitting some concerns about MS terms of use.

So now I'm going to mute me because I don't want to bother people subscribed to this ticket.

By the way, this ticket got fixed, so I think will be closed soon.

Regards

[joseluisq]

I think these links can clarify a bit more the related concerns.

• VSCodium - Why Does This Exist
• VSCodium - Extensions and the Marketplace

[ghost]

Perhaps we should get a lawyer involved instead of carrying on a debate with all of our subjective opinions.

[perjahn]

How do I edit the project.json file when using snap? (the default package manager when installing codium in ubuntu 20.04). The json file is located in a snap package which has a read-only file system.

[dcalano]

Unlike @joseluisq, I do rely on a decent handful of extensions for various development things. This change has completely ruined VSCodium for me and unfortunately until there is a matching parity on the open-vsx marketplace, I will be uninstalling as it is no longer usable.

[stripedpajamas]

@dcalano the marketplace in use is an option; you can switch to the old experience by following the instructions in https://github.com/VSCodium/vscodium/blob/master/DOCS.md#extensions-marketplace

[dcalano]

@stripedpajamas "option" is definitely not a phrasing I would use. You should not have to hack the installation to fix such a regressive design decision.
Edit: Does this change persist through updates?

[stripedpajamas]

I understand that changing the extension URL is not a great user experience. It would be great if MS allowed overwriting the extension URL in settings.json but as far as I can tell that doesn't work. Since this is a product-level change, it means that future releases will overwrite any customized product.json.

I would like to better understand the experiences people are having though. I rely on a handful of extensions in VSCodium and after the upgrade those extensions didn't stop working (although they disappeared from extension search). Is this not the experience others are having? Granted that installing an extension that wasn't installed before may be a pain until Open VSX is bolstered. This definitely increases new user friction.

Our options are limited with how to deal this... changing vscode's UI during build is definitely out of scope for this project; an extension that allows people to switch their extension gallery would be great, but I don't know enough about extensions to know if that's feasible.

In regard to better advertising that this change was made (I do apologize for the upheaval the change caused), I'm thinking perhaps a pinned issue on this repo with instructions on how to mitigate the most common issues would help.

[dcalano]

Thank you for your response and clarity. My development environment is setup via automated scripting and when I went to stand up a workstation it failed to install my old extension list via command line. I thought my script was messed up and went to check the extension store and at first thought there was an error on my computer because some extensions were present. I only noticed something fishy after manually trying to install from my list to find most of them were completely missing. I do like the lack of telemetry but some extensions such as liveshare are useful for teams and unfortunately proprietary. The unfortunate reality of our current state of surveillance capitalism is that it is virtually impossible to have 100% privacy and transparency. My use of VSCodium was to help minimize unnecessary tracking, with the understanding you can't completely cut it out without sacrificing functionality.

[t-fritsch]

Since this is a product-level change, it means that future releases will overwrite any customized product.json.

Thank you for this clarification even if it's no good news :(
What about previously installed extensions updates ? Do they keep working ?

I would like to better understand the experiences people are having though.

As already mentioned my use case is pretty simple : I'm teaching development and installing VSCodium is part of the prerequisites for my courses. After installing VSCodium, I ask them to install a few popular extensions, and this is where it fails now.

Our options are limited with how to deal this... changing vscode's UI during build is definitely out of scope for this project; an extension that allows people to switch their extension gallery would be great, but I don't know enough about extensions to know if that's feasible.

I keep thinking this change of store should be opt-in.
Disabling telemetry is one thing, completely breaking the link to the extension store is another.

The MS terms of use haven't been a problem before (the MS document says _"Last Updated January 2019"_), I can't see any reason why it should be one 1 year and a half later, and take the risk to shoot yourself in the foot. Has VSCodium team been threatened ? Maybe I'm wrong but I don't think so.

In regard to better advertising that this change was made (I do apologize for the upheaval the change caused), I'm thinking perhaps a pinned issue on this repo with instructions on how to mitigate the most common issues would help.

If the store change wasn't reverted back to MS one by default (this would be so sad if it wasn't) it definitely should be advertised as a warning on the homepage of https://vscodium.com/ in my opinion.

[GammaGames]

I have similar complaints. I use the setting sync extension to make sure my settings and extensions match up across devices, that process completely fails when trying to update. I do understand wanting to use open-vsx because it matches the goals of codium, but it is inconvenient for the time being.

Would it be possible to include a flag that would patch the product.json file so we could automate the update without grep or other similar tools? Maybe something like:

codium \
  --patch "extensionsGallery.serviceUrl=https://marketplace.visualstudio.com/_apis/public/gallery" \
  --patch "extensionsGallery.itemUrl=https://marketplace.visualstudio.com/items"

[ebell451]

Unfortunately this goes back to the age old question of Security vs Convenience. Even though there is no apparent security issues with Microsoft's marketplace VSCodium is trying to distance themselves for a number of reasons (as stated above).

@GammaGames my recommendation would be to reach out to the developers of that extension and inquire about adding capabilities for the new marketplace

@t-fritsch this would be a good opportunity to teach them how one can make modifications to some applications to work the way you would like them to work. Or, you could populate the new marketplace with the extensions you are interested in.

@dcalano based on the following why did you make the switch to VSCodium?

The unfortunate reality of our current state of surveillance capitalism is that it is virtually impossible to have 100% privacy and transparency.

[dcalano]

@dcalano based on the following why did you make the switch to VSCodium?

@ebell451 I answered that in the very next sentence...

[t-fritsch]

Come on @ebell451 are you serious ?

[ebell451]

@t-fritsch yup

[GammaGames]

@ebell451 The extension uses the VSCode API to install the extensions, the problem is that most of them aren't available in Open VSX.

[t-fritsch]

@ebell451 I can't believe you are (serious), but let me rephrase your post to try to show the nonsense :

So you're suggesting that I tell to the companies that pay me to teach their teams, and to the high-schools that I teach in, that instead of learning -let's say- react native, I'll instead teach them how to create and publish an extension for vscodium on open-vsx ? Come on...

What is in the balance here is the ease of adoption for new users, not what I should or not teach. I don't intervene in your work so please don't try to do so with mine, thanks.

[stripedpajamas]

@spoenemann

Create a pull request to this repository to have the @open-vsx service account publish the extensions for you.

Is there a reason that MS-hosted extensions have to be published in Open VSX on a case-by-case basis? Would it be feasible to mirror the MS extension gallery?

Based on the user experiences so far, it is sounding like Open VSX in its current form may be a show-stopper for new users. Brainstorming solutions.

[dcalano]

I think a good temporary solution, for now, would be to reverse the marketplace hack. Perhaps generate both a product.json and product-ovx.json, where MS's is still the default. Then users can opt-in to the open marketplace by just deleting product.json and removing "-ovx" from the other. At least while the open marketplace is still having more extensions added to it. When it gets to some sufficient parity in the future, then set it as it is now, where only the open marketplace product.json is generated. Thoughts?

[bassamanator]

When I search for extensions to install, I get a list of 10 or so items. When I look in VSCode, I get a list that doesn't seem to end.

Arch; KDE. 5.6.16-1-MANJARO

[MPLew-is]

For anyone else looking for a fix for this on macOS, I've pushed a fork of the VSCodium cask formula that resets the Extensions Gallery settings automatically during installation. All you have to do is run the following command to have this work out of the box:

brew cask uninstall vscodium && brew cask install mplew-is/vscodium/vscodium

[t-fritsch]

@kimbernator I think the VSCodium team has already well understood the problem and will be coming quickly with a solution regarding what @stripedpajamas said at https://github.com/VSCodium/vscodium/issues/418#issuecomment-650443606

[kimbernator]

@t-fritsch Yeah, you're right, I was just being snarky since I was frustrated with this change. My comment wasn't really adding anything, so I removed it.

[polyjitter]

I am in the same boat as @perjahn. Snap install, read only filesystem. Is there a workaround or are we simply out of luck?

[spoenemann]

Is there a reason that MS-hosted extensions have to be published in Open VSX on a case-by-case basis? Would it be feasible to mirror the MS extension gallery?

@stripedpajamas The MS Marketplace Terms of Use would not allow that.

[aidbal]

Quick workaround:

Edit /usr/share/codium/resources/app/product.json:

Replace:

  "extensionsGallery": {
    "serviceUrl": "https://open-vsx.org/vscode/gallery",
    "itemUrl": "https://open-vsx.org/vscode/item"
  },

with:

  "extensionsGallery": {
    "serviceUrl": "https://marketplace.visualstudio.com/_apis/public/gallery",
    "cacheUrl": "https://vscode.blob.core.windows.net/gallery/index",
    "itemUrl": "https://marketplace.visualstudio.com/items"
  },

If somebody is looking where to find product.json on macOS:
/Applications/VSCodium.app/Contents/Resources/app/product.json

[SkeLLLa]

Switching users to something that has dramatically less features/extensions than it was before - is just big UX fail.

The correct way of implementing such feature:

1. Create independent registry.
2. Add feature to allow it proxy requests for not found packages to upstream like MS marketplace.
3. Add option to settings that will allow users to get extensions from upstream if they want (you can disable it by default).

As a good example you can refer to verdaccio - self hosted npm.

I think with current implementation this "feature" will not gonna live.

[DavidSmolinski]

Instructions for the possibly illegal fix should be announced after updates.

I used phd's fix with this path.
VSCodium/resources/app/product.json

[polyjitter]

Could you explain what you mean by possibly illegal?

[kimbernator]

Yeah, not sure legality would be a real concern here. As other discussions on this have pointed out, the code pointing to those URLs has been published under the MIT license. Aside from that, this comment at the very least gives people plausible deniability if Microsoft suddenly decides to stop forks from accessing their extension gallery.

[rojnwa]

Wrote a little python script which automatically reverts the changes to the old marketplace.

You just need to adjust the first variable file_path to your actual path to the product.json
(there is probably a nice way to find that os-independently but this was just a small script I wrote in the middle of the night)

https://gist.github.com/rojnwa/976ecf2bde0b09bfd64a6f26f7101d7e)

[dalisoft]

Wrote a little python script which automatically reverts the changes to the old marketplace.

You just need to adjust the first variable file_path to your actual path to the product.json
(there is probably a nice way to find that os-independently but this was just a small script I wrote in the middle of the night)

https://gist.github.com/rojnwa/976ecf2bde0b09bfd64a6f26f7101d7e)

Thanks @rojnwa for simple and elegant solution. I used your script to my Ansible playbook and it works fine.
I modified little part of code to support macOS too.

See and copy from here.
Executing: sudo python3 fix-codium.py

Hope this helps anyone

[Sleepful]

Wrote a little python script which automatically reverts the changes to the old marketplace.

You just need to adjust the first variable file_path to your actual path to the product.json
(there is probably a nice way to find that os-independently but this was just a small script I wrote in the middle of the night)

https://gist.github.com/rojnwa/976ecf2bde0b09bfd64a6f26f7101d7e)

For windows, replace the file_path line with: file_path = "C:/Program Files (x86)/VSCodium/resources/app/product.json"
Run git bash as administrator, then python yourscriptname

[personaaleatoria]

This is also happening in 1.47.3 flatpak version and 1.48.0 appimage.

[personaaleatoria]

it works now

[Snooz82]

i really think that this is a bad move.
Sorry!

But this lead me to throw VSCodium away and install VSCode.
from one day to another i could not find the Extensions i was using normally!
i tried to analyze it but didn't directly find a solution, so i tested VSCode and this worked fine...

Open-VSX may be a nice place, but for me it caused some problems!
i would like to see some kind of a switch in the GUI to select the Marketplaces that are configured.

I now fix this but it was even not easy to find this thread here when searching for this issue...

[stripedpajamas]

I understand that this marketplace switch presents a regression since there aren't nearly as many extensions available from Open VSX as there are from MS. Much appreciation to anyone submitting ad-hoc solutions for using the MS marketplace -- I encourage the people in this thread who have come up with methods to submit PRs to the README/DOCS so that others who want to use Microsoft's marketplace can possibly have that option without digging through issues.

VSCodium will be sticking with Open VSX for the foreseeable future. I said from the beginning (on the README since almost first commit) that VSCodium would use Microsoft's extension marketplace until there was an open source alternative.

Ideally MS would allow extension marketplace to be configured in the app's settings instead of baked-in at build time. I'm not sure if this is on their roadmap (but doubtful since they will want everyone using their proprietary marketplace).

Closing this issue for now (although feel free to comment if I've missed something still pending in this issue). I will create a readme banner or issue template so that it's easier for anyone unaware of this change to figure out what happened in recent versions.

[aaronrancsik]

Is there any way to make in permanent? After every update I have to

Quick workaround:
Edit /usr/share/codium/resources/app/product.json:
Replace:

  "extensionsGallery": {
    "serviceUrl": "https://open-vsx.org/vscode/gallery",
    "itemUrl": "https://open-vsx.org/vscode/item"
  },

with:

  "extensionsGallery": {
    "serviceUrl": "https://marketplace.visualstudio.com/_apis/public/gallery",
    "cacheUrl": "https://vscode.blob.core.windows.net/gallery/index",
    "itemUrl": "https://marketplace.visualstudio.com/items"
  },

If somebody is looking where to find product.json on macOS:
/Applications/VSCodium.app/Contents/Resources/app/product.json

Is there any way to make it permanent? I mean after every update I have to manually change it back to MS store.
I can write an update hook for it, but I curious about an easier and more elegant way. :smile:

[stripedpajamas]

Not atm, at least that I'm aware of. Honestly MS should just make marketplace a setting instead of a "compile-time" var.

[caasi-dev]

Same issue using VSCodium v1.46.0 on ArchLinux.

Temporary workaround:
Update product.json file following @phd's comment: #418 (comment)

File: /usr/share/vscodium-bin/resources/app/product.json

OR

/usr/lib/code/product.json if you install the open source version community/code