How to remove outdated servers from All Servers list?

[janihur]

This is similar to #213 but for All Servers.

All Servers have many outdated servers that seems to be impossible to remove. There is "Edit Settings" in the pop-up that takes me to the correct user settings.json file but the edits there have no effect. Can we have here similar "Remove from" functionality than in Recent section?

This is cosmetic but annoying in long term.

I'm running VSCode in Windows 11.

[isc-bsaviano]

Hi @janihur, can you provide a screen recording showing that removing server definitions from the settings.json file and then saving it does not cause the Servers tree to update? I cannot reproduce that.

[isc-bsaviano]

Hi @janihur, is this still an issue? If so, can you capture a screen recording?

[janihur]

I have shared a screen recording privately with you @isc-bsaviano.

There you can see a case where I can remove one server in settings.json and the Servers tree updates and a case where there is no matching server definition in settings.json but the server still exists in Servers tree.

[janihur]

I can confirm that when I add a new server directly to settings.json it will be synced to Servers tree. The server also disappears when the entry is removed from settings.json. This works as expected.

However I seem to have a few server entries in the Servers tree without matching entry in settings.json that I can't delete. I tried to to create an entry for those servers into settings.json and then remove it but that trick didn't work. It looks like those server definitions are in some other location, maybe in a caché of some kind?

[isc-bsaviano]

Hi @janihur, I didn't receive your screen recording. Which sub-tree is the mysterious server definition under?

[janihur]

Hi @janihur, I didn't receive your screen recording. Which sub-tree is the mysterious server definition under?

I just made second try. Gee it's hard to share files ...

The sub-tree in question is All Servers (as the title indicates).

[gjsjohnmurray]

Does your File menu have a Close Folder option near the bottom? Or a Close Workspace? If so, please use it, then recheck the All Servers tree.

[janihur]

Does your File menu have a Close Folder option near the bottom? Or a Close Workspace? If so, please use it, then recheck the All Servers tree.

Yes there is:

Menu: File > Close Folder

but no luck - those ghost servers are still there.

[isc-bsaviano]

@janihur I received and watched your video. Since you already had the user settings opened when you clicked Edit Settings on the affected server and the cursor moved within that file means that VS Code thinks that server is defined in your user settings. It just couldn't find the definition within that file. Is it possible you have two intersystems.servers blocks in that file?

In the latest version the extension (3.10.5), here's the order that servers are added to the tree:

1. Servers defined in user and workspace settings
2. Servers defined in any client-side workspace folders

Servers are only added once, and any server defined in a client-side settings.json file will have the folder name in parentheses following the server name. Since your affected server does not have a parenthetical and removing the workspace folder at John's suggestion didn't help, it must be defined at the user level.