go to post John Murray · Oct 3 If the user I authenticate with doesn't have USE permission on %Service_Login you don't even try, which means I get a terminal session with the username and roles (typically %All) of the account IRIS runs as. I have raised https://github.com/caretdev/iterm/issues/2 about this.
go to post John Murray · Oct 3 What about if you are logged into Linux as the userid which your IRIS runs as? On a default install it's typically irisusr, and on the containerized IRIS instances @Dmitry Maslennikov probably uses it's typically irisowner. Here's what I find when I successfully connect to a Docker container created from a DC registry image, authenticating as SuperUser/SYS Node: d2ba2ec8dbce, Instance: IRIS USER>w $zv IRIS for UNIX (Ubuntu Server LTS for x86-64 Containers) 2024.1 (Build 262U) Thu Mar 7 2024 15:36:40 EST USER>w $username SuperUser USER>!whoami irisowner USER>
go to post John Murray · Oct 2 @Jeffrey Drumm I think your issue is likely to be that the app apparently assumes this OS-level command will lead directly to an IRIS shell prompt without requiring credentials. On Linux this means the %Service_Terminal service is accepting Operating System authentication. There must also be an IRIS user definition that matches the OS username under which IRIS runs, and that user must have sufficient rights. Enabling login-related audit messages may help you diagnose failures in this area: /path/to/iris/bin/irisdb -s/path/to/iris/mgr
go to post John Murray · Oct 2 Are you able to launch an IRIS Lite Terminal onto this server from inside VS Code? Testing this could rule out it being an issue with websockets.
go to post John Murray · Oct 2 @Jeffrey Drumm does this also happen if you launch iterm from a private browser session?
go to post John Murray · Oct 2 Browser devtools network trace shows this repeatedly: oops: <PYTHON EXCEPTION> 246 <class 'ModuleNotFoundError'>: No module named 'termios'
go to post John Murray · Oct 2 Has anyone here succeeded in making this work with 2024.1 or 2024.2 on Windows? I've tried two separate IRIS instances, and in both cases I only get a blank black page after IRIS authentication.
go to post John Murray · Oct 1 Disappointed that you have picked such a US-centric time for this, so I won't be able to participate. Thank you for rescheduling the meeting.
go to post John Murray · Oct 1 It seems that sometimes the first command you issue after opening the tab doesn't run. Please try `version` twice. After you get the version response try using other commands.
go to post John Murray · Oct 1 @Evgeny Shvarov re #3 when you write git-source-control are you referring to this package? https://openexchange.intersystems.com/package/Git-for-Shared-Development... Is using this with the client-side paradigm a supported mode? I haven't yet found any documentation to that effect.
go to post John Murray · Oct 1 @Evgeny Shvarov re #1 aren't you already using the "objectscript.conn.docker-compose.service" and ""objectscript.conn.docker-compose.internalPort" settings? If you're finding a specific problem using these please open an issue at https://github.com/intersystems-community/vscode-objectscript/issues
go to post John Murray · Oct 1 Since the Cody people talk about "the repository" I'm guessing they mean a local Git repository. When you're using ISFS you're using the server-side editing paradigm, so no local Git repository is involved.
go to post John Murray · Sep 30 The missing `set` was because I had copied the wrong line from my shell session. I have edited the post to correct this. I get the same as Jeff, so it seems the zpm install installed the requirements OK. Thanks for adding the BYOP doc to the wiki.
go to post John Murray · Sep 30 Continuing at https://github.com/intersystems-community/vscode-objectscript/issues/1437
go to post John Murray · Sep 30 Setting this up on a 2024.2 Windows instance hasn't been easy, and even now I'm only getting a blank page like @Jeffrey Drumm reported elsewhere on this thread. His IRIS was 2024.2 but not on Windows. Hurdles were: zpm 0.7.2 was failing because 2024.2 on Windows doesn't bundle pip. I got a bit further by upgrading to 0.7.3 which shipped last week. zpm 0.7.3 wouldn't install iterm until I'd gone through the Flexible Python Runtime setup steps and also worked out for myself the extra zpm steps (did I overlook documentation for these?): zpm:%SYS>config set UseStandalonePip 1 zpm:%SYS>config set PipCaller "C:\Program Files\Python312\Scripts\pip.exe" So now I have it installed in %SYS (thanks to the tip from @Evgeny Shvarov in this thread): zpm:%SYS>list zpm 0.7.3 iterm 0.1.0 zpm:%SYS> But still the blank page. And I'm wondering why the iterm contest entry mentions WSGI but the /iterm app set up by the installer is a REST one rather than a WSGI one. So far, no gain in return for the pain, and I'll continue to get along with Lite Terminal that's built in to the VS Code ObjectScript extension. It requires zero config and works on 2023.2+
go to post John Murray · Sep 29 A second article for IPM in VS Code, which now supports the use-case where a dev is using an IRIS container to import their local sources to.
go to post John Murray · Sep 28 Please see my reply at https://github.com/gjsjohnmurray/iris-package-manager/issues/2#issuecomm... to the GH issue you created.
