Adding @sandy081 since @joaomoreno is out on vac.

Looks like showing updates for locally installed extensions was never working. The only way for now to update such extensions is

• Search for that extension and Install it from market place

When syncing installed extensions with gallery extensions we are using id as mapper which is available only for extensions installed from gallery.

Fix is to use identifier publisher_id.extension_name which maps any installed extension with gallery

@joaomoreno FYI

@sandy081 @egamma would this be a candidate?

@dbaeumer This is neither a candidate nor important. It's barely a bug. It's a feature we never supported. In order to benefit from its updates, you must install an extension from the gallery. Installing a VSIX is an extraordinary, exceptional, out-of-normal situation. At least this is our current story.

An argument which supports this is the fact that anyone can just come up with the same publisher and extension names as the ones in the store for their VSIX. We don't want to have situations in which we overwrite something we should not.

@sandy081 I suggest to revert this change.

This is definitely not a candidate (hence set to January). But IMO, this looks to me a bug from an end user point of view. In this scenario, As an user, I expect an extension to show update or to distinguish local (VSIX) with Gallery extension. I would not suggest to have another category of extensions instead it makes much sense to get it sync with market place.

If disagreed, I will revert the fix

I look onto this form a user perspective. Since the market place is not allowing us to have an insider channel I ask ESLint extension users to install the vsix to help me testing new features. However now all users that did this are stuck and they don't even know about this since I didn't know about this. They are not receiving an new updates anymore

@joaomoreno if this is working 'as-designed' could you please let me know how I should ask existing ESLint extension users to participate in new version testing.

@dbaeumer Not supported, but tracked: #15756. If we want it badly, I believe we should support it from the Marketplace.

@sandy081 I can't be sure that this change won't break existing users, since we now may be matching against some extensions that the user has installed locally and he didn't intend to.

Fix reverted

Closing as duplicate of #15756

Let's fix this for February.

@joaomoreno Pushed the reverted fix.

Verified, but found #21375