open-vsx.org
open-vsx.org copied to clipboard
EclipseFdn
Problem with two different publications of the same extension
Hello! I have a problem with two versions of the same extension that are published on the openvsx marketplace:
I would like to keep only learn-pack and remove learnpack
This is puzzling. When I examine the learnpack namespace, I see this:
But when I attempt to access the LearnPack extension in that namespace from the admin panel, I see this:
Same thing happens with learn-pack. @amvanbaren @eclipsewebmaster, am I missing something?
@kineticsquid The extension name is learnpack-vscode. It can be found here: https://open-vsx.org/api/learnpack
The webui shows the extension display name. Maybe we can add a tooltip or code block to show the extension name? Or allow searching by extension display name in the admin panel?
@amvanbaren thanks for the pointer. What you suggest could be helpful, but not necessary right now. I can use a url of the form https://open-vsx.org/api/{namespace} to get the names of the extensions.
@alesanchezr, I just removed 0.0.1 - 0.0.7 of learnpack.learnpack-vscode.
@amvanbaren Is there a way to remove a namespace? Assuming there is, @alesanchezr do you want me to remove the learnpack namespace?
There's a OrphanNamespaceMigration. It cleans up namespaces without extensions. https://github.com/eclipse/openvsx/blob/8bf1d23af572aebe2321f304ea605ceb6b8f0923/server/src/main/java/org/eclipse/openvsx/migration/OrphanNamespaceMigration.java#L44-L47
Does it run automatically? learnpack namespace is there with no extensions.
It runs on server startup. An orphaned namespace is a namespace without any members. https://github.com/eclipse/openvsx/blob/8bf1d23af572aebe2321f304ea605ceb6b8f0923/server/src/main/java/org/eclipse/openvsx/repositories/NamespaceRepository.java#L25-L26
I don't know 100% if this is possible, but you might be able to delete all namespace members in the admin panel.
Ok, I have a small fix for production: https://github.com/EclipseFdn/open-vsx.org/pull/1343 When approved, I can deploy it to production. The new deployment should then delete the learnpack namespace after the server started.