@Michael Hampton
I need more info about your exact setup to answer your question. What were your export settings previously? What folder within your workspace are your InterSystems files in? Are you sure that the file that contains the definition has a local copy?
I believe this is the same problem described here. You need to add the --check-caps false command to the iris container in your docker-compose.yml file, like this:
...
iris:
command: --check-caps false
init: true
...
The SAM 1.1 distribution should have this done for you but that change must not have made it in. I think you can still enter the SAM 2.0 EAP if you'd like to start with the upcoming version.
The logs are stored in the containers themselves. Using docker you can read them using the docker logs command. According to the podman docs, this is what you would need to run:
podman logs sam_iris_1
@Scott Roth
I don't use podman so I'm not sure how to check this but it looks like the SAM Manager container (a modified IRIS) is not up or is not healthy. Can you check if it's up and if so, check the log contents? Nginx is probably reporting a bad gateway error because the SAM Manager isn't listening on the expected port
@Scott Roth
SAM or Prometheus alone can be installed on a separate server. They just need network access to the IRIS servers that you want to collect metrics from.
@Gertjan Klein
Unfortunately that's not supported and I'm not aware of any way to support that.
@Michael Davidovich
Refreshing the explorer only refreshes the nodes in the tree view. If you have a virtual file open that you opened from the explorer it won't auto-update. You can close it and reopen it and the extension should fetch the new copy. If you have your local copy open, you can export again to get the latest version.
@Michael Davidovich
If you have a local folder open there should be two tree views within the ObjectScript view container (the left pane that is shown after clicking the InterSystems logo in the activity bar on the far left). The bottom one is the Projects Explorer and it's only used to create/modify/export server-side project contents (also known as Studio Projects). The top tree (with the Explorer name) is the ObjectScript Explorer where you can Compile/Export/Delete packages and files. Since you don't use server-side source control and need files in your local file system, you can safely ignore the Projects Explorer since they won't be useful for your workflow. Here's a screenshot of what this looks like for me in a locla folder called "langauge-server":
EDIT: If the ObjectScript Explorer isn't showing, make sure you don't have the setting "objectscript.showExpolorer" set to false.
@Michael Davidovich
You can export individual packages or files from the ObjectScript Explorer. Simply right-click on the node(s) that you want to export and click the "Export" menu option. The command may be better in your use case though because once you have your settings configured properly, you don't need to do anything else besides run the command to update your local copies.
Unfortunately there isn't a way to automatically update your copy if changes are detected. If you make an edit and then try to save it to the server the extension will check if there's a conflict and help you resolve it. If you are working client-side then I wouldn't expect a server conflict though because your local copies (synced with source control of course) should be the "source of truth". You can always re-run the export command before you edit if you want to avoid conflicts.
As for the disappearing disp class, editing the impl class will not force the disp class to be regenerated so its state shouldn't change. That may be due to your Studio configuration being set to hide generated files.
As a first step I suggest you read through our online documentation to familiarize yourself with common workflows. The extension supports a client-side workflow where you export files to the currently open local folder and handle the source control yourself. To edit client-side, you can use the ObjectScript Explorer to export files. You can also use the Export Code From Server command, which uses the objectscript.export configuration settings to determine what to export. Our extension does not support VS Code's "Download" menu option.
Since the disp class is generated from the spec class you probably don't want to store it in source control but if you still want to export it, you can have the Explorer show generated files before you export a package or if you're using the command you can set the objectscript.export.generatedto true.
@Henry Wojnicki
I'm glad you like the extensions! If you send me an example of the syntax coloring bugs via email (or post an issue on the Language Server GitHub) I will try to fix them for you.
@Jonathan Lent
Starting in IRIS 2020.1.2, 2021.1.1 and 2021.2 you can directly drill down into objects and see all of their properties during debugging. If a variable is an object, you will see its class name in grey next to it and an arrow to expand it like you would a folder in the VS Code file explorer view. This new feature is shown around timestamp 3:30 in this Learning Services produced video on debugging using VS Code.
That's great! Happy to help
@Kari Vatjus-Anttila
Can you please download and install the version of the extension found here and check if that fixes the issue? To install it you can drag it from your downloads folder into the extensions view in your VS Code window.
@Peter Steiwer
If you're working server-side, you can add the "generated=1" query parameter to your folder URI to see generated files: https://intersystems-community.github.io/vscode-objectscript/serverside…
@Jeffrey Drumm
Sorry, I assumed you were asking this in the context of CI. AFAIK the only way to do this is what I described. If you would like a way to do this using server-side editing, please file an enhancement request issue in the GitHub repo.
@Jeffrey Drumm
VS Code isn't a CI/CD tool so it wasn't specifically designed for this but it is doable if you're working client-side. You can export files from one namespace, change the namespace in your settings.json file and then import and compile.
I'm sorry, I misread the end of your post.Can you please answer Julian's question below? If the class is saved then the formatter should work.
You should install the InterSystems ObjectScript Extension Pack to get full support for ObjectScript in VS Code. The InterSystems Language Server provides formatting support. You can view our documentation here and the Language Server README here.
Before SAM, there was no way to monitor Cache or IRIS using Prometheus out of the box. You had to implement the metrics exporter API yourself or use a community implementation like the one you linked. Since 2020.1, the /api/monitor API is provided by InterSystems out of the box. SAM uses this API to collect metrics and alerts from servers.
@Michael Lei That is a community tool that predates SAM and is not supported by SAM. The /api/montior API that was developed for SAM (but can be used by any tool that consumes Prometheus metric format) is only included in IRIS 2020.1+.
Yes, that's expected behavior. The vscode-objectscript extension defines the languages based on file extensions:
{
"id": "objectscript",
"aliases": [
"ObjectScript"
],
"extensions": [
".mac",
".int"
]
},
{
"id": "objectscript-class",
"aliases": [
"ObjectScript Class"
],
"extensions": [
".cls"
]
},
{
"id": "objectscript-macros",
"aliases": [
"ObjectScript Include"
],
"extensions": [
".inc"
]
},
{
"id": "objectscript-csp",
"aliases": [
"ObjectScript CSP"
],
"extensions": [
".csp",
".csr"
]
},
Hi Julian,
I just opened up my VS Code (version 1.61.2 on Mac, latest version of all 3 extensions) and tried formatting a class and mac routine and it worked both times. Can you confirm that the Language Server extension is enabled? Also, what's the extension of the file that you're trying to format?
@Julian.Matthews7786 The Language Server extension includes an ObjectScript formatter with the following features:
You can invoke it like any other formatter in VS Code. This VS Code doc page has more information on formatting in VS Code. The Language Server README has more info on its features and configuration settings.
@Muhammad Waseem Atelier is deprecated. VS Code is the recommended IDE for new ObjectScript developers. See this post for details.
@Michael Lei SAM (or standalone Prometheus) can only monitor IRIS version 2020.1 or later.
Do you have the file exported to your local file system already? If not, then you'll have to set the serverSideEditing setting to true for the server copy that gets opened to be editable.
@Dominic Chui Please try issue #2 again using LS version 1.1.6 and vscode-objectscript version 1.0.11. To diagnose issue #1, I'll need the text of the routine that you're seeing the "class does not exist" error in. Please submit an issue at https://github.com/intersystems/language-server/issues with a code sample.