go to post John Murray · Oct 21, 2022 In the Extensions view if you search for "intersystems" does it offer you the option of installing the extensions into your container? Or have you already done that?
go to post John Murray · Oct 21, 2022 Probably our biggest pain point related to InterSystems software upgrade, and one we have to try and make sure sites using our Deltanji source code management tool are aware of, is that the procedure can result in class dictionaries of remote databases being upgraded to a dictionary version that the instance hosting the databases cannot handle. Our Deltanji documentation now includes this paragraph in the section about InterSystems platform upgrades: Before upgrading an InterSystems IRIS, Caché or Ensemble instance we strongly recommend that you first disable all ECP connections the instance makes to other instances. Leave these connections disabled until after you have completed the upgrade, including execution of any post-upgrade steps recommended by InterSystems such as the recompilation of code in all namespaces. These precautions should prevent the upgrading instance from inadvertently upgrading class dictionary entries and routines on remote instances which may still be running an earlier InterSystems platform version.
go to post John Murray · Oct 4, 2022 And for extra convenience, follow the steps given in the Extension's README to enable the use of proposed APIs (view them here, or on the Details tab of the extension's page in VS Code). Then you can use the VS Code quickpick that Ctrl+p or Cmd+p opens (NB unshifted 'p'), type `String` and you should be able to open it directly.
go to post John Murray · Oct 4, 2022 Here's what I recommend (assumes you are using Server Manager extension as well; can be done without it but you'll have to edit JSON in a file): In Server Manager's tree, expand the namespaces of your server. Clock the "eye" icon on the %SYS row. This will add another root folder to your VS Code workspace. The folder uses the `isfs-readonly` scheme to access the namespace directly. In VS Code's Explorer (not ObjectScript Explorer), expand that folder and drill down to find the class you want. Assuming you want to use this multi-root workspace again, use "Save Workspace As..." from the File menu. If you don't, you'll be prompted when you exit VS Code and given a choice of saving or discarding.
go to post John Murray · Oct 4, 2022 Good video. One tip I have is that at 4:18 it advises using a command to add second and subsequent folders to a multi-root workspace. Instead I recommend clicking on the InterSystems Tools icon in the Activity Bar, then using the Servers tree (contributed by the Server Manager extension) to find your server and namespace, then clicking the pencil button (Edit Code in Namespace). This adds an isfs entry to your workspace. The eye button alongside it will add an isfs-readonly entry instead. Indeed you can do the whole of the workspace creation from that tree. With nothing open in VS Code (no folder, no workspace) click all the pencils or eyes you want. To name and save your workspace use "Save Workspace As..." from the File menu. If you haven't done that by the time you close the VS Code window you will be prompted to save or discard the as-yet-untitled workspace. So if you just wanted to browse a server speculatively you can use an untitled workspace and discard it when you exit.
go to post John Murray · Sep 28, 2022 How intriguing Rob. May I suggest you edit the post and change the language at the top of the CodeSnippet elements so they're set to JavaScript instead of ObjectScript? Or if you prefer, ask me and I'll do it using my DC Moderator powers.
go to post John Murray · Aug 24, 2022 It won't necessarily be the instance name, depending on how the external web server has been set up.
go to post John Murray · Aug 24, 2022 Documentation at https://intersystems-community.github.io/vscode-objectscript/configurati... has now been updated to include this information.
go to post John Murray · Aug 24, 2022 In the intersystems.servers object in your settings JSON you can add a pathPrefix property within the webServer object of your connection definition. In your example: "intersystems.servers": { ... "server1": { "webServer": { "host": "localhost", "port": 443, "scheme": "https", "pathPrefix": "/instance1" } }, ... }
go to post John Murray · Aug 8, 2022 Please open an issue at https://github.com/intersystems-community/vscode-objectscript/issues Screenshots can be pasted from clipboard direct into GitHub. Thanks.
go to post John Murray · Aug 5, 2022 Interesting. Based on doc at https://docs.intersystems.com/healthconnectlatest/csp/documatic/%25CSP.D... the common attribute of all the faultily-displaying properties is that they are calculated. Does that hold true for the ones not shown in your screenshot?
go to post John Murray · Jul 28, 2022 Turns out it wasn't hard to add this. Download and install 1.8.2-beta.2 if you want to try it out. Only the editable file gets coloured, not the preview. It may be possible to address that, but would require more work than I have time for at the moment.
go to post John Murray · Jul 25, 2022 Were you logged in as a user with the %All role when you clicked the update link in WebTerminal?
go to post John Murray · Jul 21, 2022 I haven't seen this problem. The GitHub source of this method doesn't seem to check the status of its ParseStream call before trying to read the stream: Maybe your upgrade procedure went wrong. I suggest you download the XML distribution and import it again.
go to post John Murray · Jul 21, 2022 One way is to use my webterminal-vscode extension in conjunction with the WebTerminal package.
go to post John Murray · Jul 19, 2022 An example is shown in https://community.intersystems.com/post/use-serenji-debug-your-rest-serv...
go to post John Murray · Jul 19, 2022 The Serenji VS Code extension from George James Software supports direct backend debugging of REST endpoints in Caché and InterSystems IRIS. The debugging features of Serenji require an activation key. We provide free 30-day keys upon request. John MurraySenior Product EngineerGeorge James Software
go to post John Murray · Jul 19, 2022 Maybe you need to sign up on the Columnar Storage Early Access Program at https://gs2022.isccloud.io/#early-access
go to post John Murray · Jul 11, 2022 Instead of adding the %All role to the /terminalsocket web app I suggest you add %DB_IRISLIB which should be sufficient to solve your issue. My guess is, this environment used to give public %DB_IRISLIB:R but then someone tightened security by removing this, around the time you upgraded WebTerminal. Such a change ought to show up in the audit log.
go to post John Murray · Jul 11, 2022 UnknownUser is normal for the /terminalsocket session. Does the problem also occur if you start from an incognito/InPrivate instance of your web browser? Previously you reported that WebTerminal is working OK on another of your InterSystems environments. Is this still the case? Is that one using 4.9.5 yet? For the one that fails to make the websocket connection I suggest you use F12 in your browser to open Developer Tools, and make sure network tracing is active before you go to the /terminal/ URL to open a WebTerminal. Look at the network trace messages, and compare them to equivalent messages from a different web browser session that connects successfully to WebTerminal on your other environment. I'm not clear whether WebTerminal ever worked on this InterSystems instance, e.g. with WebTerminal 4.9.3. Maybe also worth checking what the InterSystems security audit log is showing around the time you fail to connect with WebTerminal. You may need to turn this auditing on, and perhaps enable it for some additional event types.
