Direct use by the VS Code / Windsurf etc "vibe coding" features of resources with `isfs://` type URIs (i.e. server-side classes etc living only in an IRIS namespace) seems to be blocked by https://github.com/microsoft/vscode/issues/277970

Re the AD lockout caused by saved passwords, I assume this was after you had changed your AD password. After doing that did you use the Accounts button at the bottom of the VS Code Activity Bar to sign out the connections that used this AD account,  and opt to delete the saved password for each?

You may be able to avoid having to install anything on the server by using the /action/query endpoint of the /api/atelier API to run a SQL query such as this:

SELECT
 p.Name AS Project,
 p.Description,
 pi.Name AS Component,
 pi.Type
FROM
 %Studio.Project AS p,
 %Studio.ProjectItem AS pi
WHERE
 p.Name = pi.Project
ORDER BY
 Project,
 Component

as before CSP and SMP

I am confused. The original post says:

No Management Portal or Web Services
The entire CSP/web stack is removed.

I received this message on Discord from one of the InterSystems team:

Demo cloud service doesn’t work for now, we disabled this feature. But you still can provide demo on your own server.

This text needs correcting, and not just because of the inconsistency about how many points an online demo is worth:

In your example does IE.cls represent your interop production class? One of the longstanding source control challenges of the InterSystems interop architecture has been the monolithic nature of the prodclass. Deltanji transformed the scene a few years ago by implementing source control at the level of the individual business hosts within the prodclass.

Unless your project and my project overlap on one or more business hosts, we can work alongside each other in a shared development namespace and each promote our work to test (and ultimately to prod) independently.

I might be on a road to nowhere though, given the problems I've been finding. I wonder if this'll qualify me for the "Find and report a bug" bonus 🤞

So, a bit confusing that Open Exchange sent out an email just now saying that the voting is open, and closes on 7th December...

Maybe a consequence of Thursday being the US Thanksgiving holiday. 

Many thanks for this. I have now published a new release of the gj :: configExplorer extension that works in VS Code on Windows.

For the record, this was resolved at https://community.intersystems.com/post/vs-code-find-routines

Having read the "lively" thread discussion as it has developed so far, my suggestion is that the form should ask the poster if the report can be made public. If yes, then after it has been reviewed (by ISC staff? DC moderators?) for security implications it can be made public if there are none.

@Dmitry Maslennikov do you intend to address any of the 5 open issues on the iTerm repo, one of which is IMO a significant security vulnerability I reported more than a year ago? 
​​​​​

Ah, so I assume you reverse engineered the unpublished TCP protocol that the published Native API packages use, right?