General questions or comments about the extension are also welcome on this DC thread.
We're starting to think about the next iteration of this extension. If you have any bug reports or enhancement requests please post them at https://github.com/intersystems-community/vscode-iris-jupyter-server/is…
General questions or comments about the extension are also welcome on this DC thread.
They got back to me. Clearing browser cookies from isccloud.io did the trick, after which I was offered "demo" rather than "micro".
I tried again just now and hit the same problem. @Ben Spead do you know if it's supposed to have been fixed?
I guess you are looking for a way to launch the XML Schema Wizard add-in that Studio offers.
Try adapting the advice at https://docs.intersystems.com/components/csp/docbook/DocBook.UI.Page.cl… for adding a custom entry to the Server Actions menu. In this case the entry in the "links" object within "objectscript.conn" should be:
"Open XML Schema Wizard": "${serverUrl}/isc/studio/templates/%25ZEN.Template.AddInWizard.XMLSchemaWizard.cls?$NAMESPACE=${ns}"Thanks for following up Ben.
If you have a 2023.2 instance maybe try this:
https://community.intersystems.com/post/there-something-similar-studio-…
I recommend you contact WRC for help. They should be able to investigate this with you. Then if it looks like there's an issue with the InterSystems ObjectScript extension or the Server Manager one (or just possibly the Language Server) they can help you log it on the corresponding GitHub repository, or can do that on your behalf.
People interested in a better testing experience in VS Code may like to support this idea I posted recently:
Maybe try this extension.
If you're using 2023.2 there's a built-in WebSocket Terminal feature, with a convenient way to launch these terminals from the Namespaces tree of Server Manager:
.png)
However it's only the :+1: 👍that counts towards moving from Backlog Candidate to Backlog.
I'd argue this breaks rule #2 by switching language (it says "including but not limited to").
How much memory have you allocated for database cache (global buffers)?
What do your GLOSTAT figures look like?
I confirmed that the Community Edition containers (at least, the one I checked) still include a PWS 👍
Was there a problem with the voting earlier this week? I know of two people who voted on Monday but when they re-checked yesterday or today found that their votes were no longer registered, so they had to vote again.
I think something similar happened during a previous contest.
What I mean is, Package Manager acts on the file system of the IRIS instance (aka server) in which you run it.
Yes, you can install a snippets package using that approach, but you will probably want to arrange that the code-snippets files end up where VS Code needs them when operating in the client-side editing paradigm.
Pinging @Daniel Tamajon
I tried to set this up for my https://github.com/gjsjohnmurray/oex-vscode-snippets-template repo, and though the workflow ran I didn't see any results. Nor does my OEx app report that it's connected.
Am I doing something wrong? Or is the structure of my code repo unsuitable? It has a cls subfolder under the src folder, for example.
Maybe try again after using InterSystems Portal to change the Source Control Class setting for the namespace to "NONE".
Thanks @Evgeny Shvarov
Since Package Manager is server-centric this puts the package author's _OEX_*.code-snippets files on the filesystem of the IRIS server you install the package into. But if you also / instead want to use them for client-centric VS Code editing you can copy them somewhere else. There's a note about this at the end of the README.
To make the contents of a .code-snippets file available to all of your folders / workspaces, put it into the snippets subfolder of the folder that contains your settings.json file. One way to locate that folder is to run the command "Preferences: Open User Settings (JSON)", then use the context menu of its editor tab to reveal the file in Finder / File Explorer. You should see a snippets subfolder there.
Alternatively, use the "Snippets: Configure User Snippets" command, choose to create a new Global Snippets file, enter a name for it (file extension doesn't need to be entered), then paste the snippets into it.
Does this work?
.png)
write sm."hello_world"()I just published 0.0.5 which supports that platform. Thanks for your interest in the extension. I look forward to your feedback.
Also here:.png)
Did you find this when you searched for "epoch" here on DC?
https://community.intersystems.com/post/how-convert-current-date-and-ti…
I'm glad to hear that. Don't know how it could have happened, unless you'd been editing the JSON directly.
I have opened https://github.com/intersystems-community/intersystems-servermanager/is… to capture the issue about the error message not being a template literal.
@Eduard Lebedyuk the presence of '$(name)' in that message is misleading because of a small SM bug. If @Michael Gosselin had tried entering exactly that when adding the definition he would have seen this:
.png)
Please use Command Palette to run "Preferences: Open User Settings (JSON)", then review the contents for any syntax errors. My hunch is the file contains an invalid JSON structure, so the extension's call to update the "intersystems.servers" object in it is failing.