This turned out to be a bug in VS Code core. The issue report can be found here: https://github.com/microsoft/vscode/issues/239350

@Marc Mundt I'll reach out to you privately.

@Marc Mundt Can you post your workspace configuration (the .code-workspace file if you're using server-side editing)? Do you see any errors in the ObjectScript Output channel? Does the package only contain system or generated classes? By default those are not shown.

Hi @Andre Ribera , AFAIK there isn't a way to check on a server if a Studio client connected to it has unsaved changes to a project. You can edit projects programmatically using the %Studio.Project class. You may also want to consider making your app IDE-agnostic because Studio is deprecated and has been removed from IRIS kits starting with 2024.2.

Hi @Olivier Caudron, happy to help! The :client-side editing" model in VS Code (editing files on the local file system) does not depend on Git. You can use it with any source control system. Because you're using Git, editing files in this way will unlock VS Code's excellent default Git integration.

Hi @Luc Morningstar, if VS Code is not meeting your needs then I would be happy to hear about how we can improve it. We take bug reports and feature requests via GitHub issues. Please see these docs on how to report issues from VS Code and which types of issues go to which extension. I would also like to note that VS Code will fail to save a class if its name differs from another class name only in case.

Hi @Olivier Caudron, The InterSystems VS Code extensions do support editing files on your local file system that are tracked by Git. The documentation for the extensions can be found here. Note that we have some major enhancements to this workflow coming in the next month or so, see this DC post for more info.

Hi @Daniele Monti, if there's no error message in the ObjectScript Output channel then you will need to capture a network trace. This will capture all REST traffic between VS Code and IRIS, so we can see the whole response to that request. I suggest you use wireshark or the Web Gateway's HTTP Trace tool. With the tool enabled, reproduce your issue. The turn the tool off and find the request that corresponds to that action. It will be a PUT on a URL like /api/atelier/v6/doc/UITXXPIEPAAdm.mac. The find the corresponding response. It should be a 40X or 500 response. Copy the entire body and post it here (hiding any sensitive information). That should tell us what the issue is.

If possible, you should use VS Code on a developer laptop that can be kept up to date instead of the server that IRIS/Cache is running on. The extension versions you are using are well over a year old and you'll be missing out on major new features, like the one you requested in this post. VS Code can connect to servers that are on a different machine.

@David Hockenbroch 
I suggest you open a WRC case to request a different way to enable SMTP tracing if the subclass or IRISLIB mounting approaches don't work for your case.

@LI LINFENG 
I also noticed that versions of the extensions that you have are very old. You should make sure VS Code and its extensions are able to auto-update so you can take advantage of bug fixes and new features.

@LI LINFENG 
The vscode-objectscript extension does not support this yet, but an enhancement that adds this feature is currently under review. You can read more about it, and download a version of the extension to test the enhancements with, on this DC post.

@Pietro Di Leo 
If you find Wireshark intimidating you can use the Web Gateway's HTTP trace facility. If you're using Wireshark and the server is on the same machine as VS Code select the loopback capture device and add an http filter. This will help you filter out unwanted packets. If you use the Web Gateway's HTTP Trace, you can simply turn it on, attempt to save the class, turn the trace off, and then click refresh to see all the packets. You will be looking for a PUT request to the /api/atelier/v#/doc/<class_name> endpoint. We want to see what the full response is to that request.

@Pietro Di Leo 
That error is a red herring. That's coming from the Codeium AI extension which doesn't like our isfs URI format. This will not affect saving the files on the server. The best way to determine why your server saves are failing would be to get a network trace using a tool like Wireshark or the Web Gateway's HTTP trace tool.

@Pietro Di Leo 
That error has nothing to do with compilation. It didn't even get that far. VS Code tried to save that file on the server, but it failed. There should be an error in the ObjectScript Output channel. If not, a network trace will show us the HTTP error response.