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 🤞

I'd like to set up an online demo of my entry, gj :: dataLoader, using the template suggested above. Yesterday I posted on Discord to request the service key as advised at https://github.com/intersystems-community/iris-google-run-deploy-templat..., but no reply yet. I assume it'll come either by DM on Discord (or here on DC), or else by email.

Since you are using a custom login class maybe the warning at https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls... is relevant:

Usually, the login page is loaded before the user has logged in to InterSystems IRIS, so the requesting process runs under the CSPSystem user (or whatever user connects the CSP Gateway to InterSystems IRIS). As a result, the CSPSystem user must have sufficient privileges to load and run the code in the login page, which generally requires READ permissions on the resource protecting the database in which the login page is located.

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.

@Stefan Wittmann - Please expedite publication of version 2.0.3 of the Node.js package, which WRC tells me will fix the problem that's been causing my gj :: configExplorer extension to crash VS Code.

https://github.com/gjsjohnmurray/gjConfigExplorer/issues/6

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.

Have you followed all the steps documented in the README to enable Proposed APIs? 

@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? 
​​​​​

Looks similar to at least part of the issue I covered in https://community.intersystems.com/post/webterminal-broken-iris-20242

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