go to post John Murray · Nov 20 @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
go to post John Murray · Nov 18 For the record, this was resolved at https://community.intersystems.com/post/vs-code-find-routines
go to post John Murray · Nov 18 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.
go to post John Murray · Nov 18 Have you followed all the steps documented in the README to enable Proposed APIs?
go to post John Murray · Nov 13 @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?
go to post John Murray · Nov 13 Looks similar to at least part of the issue I covered in https://community.intersystems.com/post/webterminal-broken-iris-20242
go to post John Murray · Oct 15 Or use the tip at https://community.intersystems.com/post/visualize-your-intersystems-serv... from @Thomas Wuppermann
go to post John Murray · Oct 15 As noted in the original post, when a Windows version of the VSIX is built and used it crashes VS Code's extension host process. I have a WRC open for this, as I suspect there's a problem with how the Windows variant of the InterSystems API package has been built. Meanwhile maybe try the steps in https://community.intersystems.com/post/how-windows-users-can-try-gj-con...
go to post John Murray · Oct 12 Ah, so I assume you reverse engineered the unpublished TCP protocol that the published Native API packages use, right?
go to post John Murray · Oct 12 I am curious to know which of the published and supported IRIS Native APIs this (the go-irisnative package) leverages.
go to post John Murray · Oct 12 gj :: configExplorer uses an IRIS Docker container for its test / demo workspace. Please see https://github.com/gjsjohnmurray/gjConfigExplorer/tree/main/test
go to post John Murray · Oct 9 The same for the idea I linked gj :: configExplorer to. Still "Needs Review" and no bonus awarded yet. 🤞
go to post John Murray · Oct 9 gj :: configExplorer now has 2 DC articles. I also claim the Find a Bug bonus for https://github.com/intersystems-community/nodejs-bugreports/issues/1
go to post John Murray · Oct 9 A couple of updates on this technique: You'll need the Dev Containers extension from Microsoft installed. We can simplify the procedure by starting with the 'Dev Containers: Clone Repository in Container Volume...' command from Command Palette. This avoids needing a local clone of the repository in your Windows filesystem. I have updated the original post.
go to post John Murray · Oct 9 There's also Deltanji from George James Software, the pioneers of the production decomposition technique.
go to post John Murray · Oct 7 It's worth noting that the extension can't currently run on Windows without crashing VS Code's extension host (EH) process and thus impacting all other extensions. More information here, which I hope qualifies my entry for the 'Find a bug in InterSystems IRIS External Languages Offerings' bonus. For Windows users there's a workaround, as long as you have SSH access to a Linux host on which you can run Docker containers. Here's what to do: Launch VS Code on your Windows desktop. If you don't already have it, install the 'Remote - SSH' extension from Microsoft. From Command Palette run `Remote-SSH: Connect Current Window to Host...`. Enter your SSH connection string in the form `user@host`. When prompted for your password (top centre), enter it. Wait for the progress notifications (lower right) to complete and for the Remote panel on the status bar (far left) to confirm that you are connected. In Extensions view, find gj :: configExplorer and install it. This action will install it on the Linux server for use of the account you connected there with. It also installs Server Manager if necessary. When operating this way gj :: configExplorer executes in an EH on your Linux server. Connections to the target servers' superserver ports will originate from there, not from your Windows device. Resolving the server names / addresses will behave accordingly.
go to post John Murray · Sep 23 Is your /api/atelier web application enabled? Is your web server configured correctly to forward that endpoint to IRIS? Did you try the steps I suggested at https://community.intersystems.com/post/cant-connect-vscode-iris4health-...?
