Unable to reopen ISFS document after closing it

[gjsjohnmurray]

Type: Bug

1. Connect to an IRIS namespace using ISFS.
2. Open a routine.
3. Close the routine.
4. Open the routine again.

A bisect through beta builds indicates the problem was introduced at 2.12.19-beta.8 which was PR #1440. That PR included migration from node-fetch to axios.

Extension version: 3.0.3-beta.9
VS Code version: Code 1.101.0 (dfaf44141ea9deb3b4096f7cd6d24e00c147a4b1, 2025-06-11T15:00:50.123Z)
OS version: Windows_NT x64 10.0.26100
Modes:

System Info

Item	Value
CPUs	Intel(R) Core(TM) i7-10510U CPU @ 1.80GHz (8 x 2304)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: enabled_on direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_graphite: disabled_off video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled webnn: disabled_off
Load (avg)	undefined
Memory (System)	15.84GB (1.73GB free)
Process Argv	--file-uri file:///c%3A/jm/VSCodeWorkspaces/DOH-VVm-VCMDEVMP.code-workspace --enable-proposed-api intersystems-community.vscode-objectscript --enable-proposed-api georgejames.vscode-deltanji --enable-proposed-api georgejames.intersystems-serverdiff
Screen Reader	no
VM	0%

[isc-bsaviano]

@gjsjohnmurray I can't reproduce this using the biggest routine I have (about 9000 lines). Can you collect a REST traffic log an email it to me? Any other tips for how I can see this.

[tinsmanj]

This is the same behavior I just started seeing when I loaded the latest VS Code version 1.101. Prior to that version things were working just fine. If I do a "Reload Window", I can then open the routine but as John indicates, if I close it and try to reopen it, I get the error message.

[gjsjohnmurray]

@tinsmanj are you using IIS as the webserver? Our current theory is that's significant.

[tinsmanj]

Yes, we do connect through an IIS server.

[gjsjohnmurray]

@tinsmanj I am about to open a WRC case about this.

[gjsjohnmurray]

WRC case is 1000909. I created it as High priority.

[isc-bsaviano]

Users who are experiencing this issue can roll back to VS Code 1.100.3 while this is being investigated.

[gjsjohnmurray]

Users who are experiencing this issue can roll back to VS Code 1.100.3 while this is being investigated.

Follow the advice at https://code.visualstudio.com/docs/supporting/faq#_how-do-i-opt-out-of-vs-code-autoupdates to disable auto-update before you roll back, otherwise you may get re-upgraded.

[isc-bsaviano]

@gjsjohnmurray @tinsmanj I just opened a PR with a potential fix. You can download a zip containing a test vsix below.

vscode-objectscript-3.0.3-dev.1584.vsix.zip

[tinsmanj]

@isc-bsaviano This appears to resolve the issue for me when I have my hosts file entry that points directly to a web server that supports our SMP. When I go through our Netscaler in front of our SMP web farm it still fails. However, my team believes that is an issue with the configuration of our Netscaler. So for me, this is now working. I'd certainly wait for @gjsjohnmurray and his results but for now very promising. Thanks.

[isc-bsaviano]

Thanks for testing @tinsmanj! I have confirmation from someone in ISC that this is fixing the problem for them as well. I anticipate doing a new release of this extension on Monday and hope to include this fix.

[tinsmanj]

@isc-bsaviano My pleasure and it appears to resolve the issues I had yesterday connecting my VSCode through "AWS SSM" to an IRIS instance on a EC2 box. I was getting exactly the same error message but after loading the fix, that issue is gone.