@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

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.

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.

Continuing at https://github.com/intersystems-community/vscode-objectscript/issues/1437

Pinging @Semion Makarov in case the extra point has been overlooked.
 

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+

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.

...and Jetpack now has a video plus a first DC article.

I submitted OEx updates to the details of both my entries earlier today, merely adding an online demo link for each. Both updates are still showing as awaiting approval. Please add that bonus to DX Jetpack for VS Code and IPM in VS Code.

Here's a technique I previously wrote up, maybe useful until IPM supports this scenario itself.

https://community.intersystems.com/post/can-zpm-ipm-package-be-required-...

No, nothing else new in it. Were you able to connect but not work? Or wasn't it possible to connect? If the latter, perhaps the server had run out of licenses.

A new version of the ObjectScript was published on Marketplace yesterday to fix this issue.

"isfs" stands for InterSystems File System. It is an implementation of VS Code's FileSystemProvider API which enables extensions to provide virtual filesystems.

More information near the end of the page at https://code.visualstudio.com/api/extension-guides/virtual-documents

I suggest you ask the Cody extension authors whether they support FileSystemProvider-sourced documents.

The clone url above seems to be for a different repo.

Anyone suffering from this and who hasn't downgraded to VS Code 1.92.2, or who has but is willing to upgrade to 1.93 again, please see https://github.com/intersystems-community/vscode-objectscript/issues/142...

Unless we get adverse reports about that beta VSIX we plan to publish a non-beta build of it on Marketplace early next week.

A couple of days ago I entered a new version of DX Jetpack for VS Code which adds three completely new extensions.