go to post Brett Saviano · Mar 1 Since this issue can't be reproduced by you on another server, or by me with a fresh install of your adhoc, I think it's highly unlikely that there's a product defect. I think this is an issue with that specific instance only. The WRC should be able to help you investigate this further.
go to post Brett Saviano · Feb 29 I tried to reproduce your issue with your exact server version and I couldn't get the error to occur. Do you remember when this started happening? Does debugging work when you connect to other instances?
go to post Brett Saviano · Feb 26 Yes, that is very helpful. The <COMMAND> error is coming from a line that calls "Do <debug_target>", which in this case is "##class(prosthetic.ProstheticResourceTest).RunTests()". Does running "Set a = "##class(prosthetic.ProstheticResourceTest).RunTests()" Do @a" work from the terminal in that namespace or do you see the same <COMMAND>?
go to post Brett Saviano · Feb 26 Thanks for the information @Daniel Raderstrong. Can you please run the troubleshooting steps found in the docs and post the contents of the trace global here? That will help me identify the cause of your issue.
go to post Brett Saviano · Feb 23 @Daniel Raderstrong How are you running the debugger? What version of the vscode-objectscript extension do you have and what's the $ZV of your server?
go to post Brett Saviano · Feb 21 @Evan Gabhart No, you can't import .rtn files and we have no plans to add that. Other than the SMP, you can use the VS Code integrated terminal to open an IRS terminal, or the WebSocket Terminal to import the .rtn files. I would recommend using a different format for your exports though, like XML or UDL.
go to post Brett Saviano · Feb 9 Thanks for the screenshots. I've never seen that happen before. I just booted up my windows machine and tried to reproduce that behavior but couldn't. If you delete the src/index.csp file and then save src/goerke/index.csp, does src/index.csp re-appear? Do you see any errors or messages in the ObjectScript Output channel?
go to post Brett Saviano · Feb 9 I'm not sure what you mean by "it recreates the file in the root directory of the namespace". Can you post a screenshot? Also, can you describe in more detail what you're trying to test? We will be able to give better advice with more context.
go to post Brett Saviano · Feb 9 @Daniel Goerke What learning course/training steps are you following? Do you mean to be creating CSP files? CSP files need to be stored inside a web application so they can be served by the web server. They can't be created as standalone files without that context. Therefore, you need to have the CSP file in folders that tell VS Code what web application it goes it. For example, if you want to create mypage.csp in web application /csp/user, the path to the file inside your local workspace should be something like src/csp/user/mypage.csp. You may also find it easier to edit web application files directly on your IRIS server using server-side editing.
go to post Brett Saviano · Feb 9 Thanks for your feedback! In response, I've submitted Pull Request #1311 which removes the comment-continuation feature for ObjectScript comments (it's still enabled for class description /// comments). It also adds auto-closing of C-style block comments (e.g. typing /* automatically adds */ after the cursor). You can try this out by downloading and installing the latest beta version of the vscode-objectscript extension from GitHub, which can be found here.
go to post Brett Saviano · Feb 7 @Evgeny Shvarov This should work: Do ##class(%Studio.General).GetWebServerPort(,,,.url) Write url,"csp/sys/UtilHome.csp" Kill url
go to post Brett Saviano · Feb 1 @Norman W. Freeman If you upgrade to version 2023.3 or newer, you can use ##class(%RoutineMgr).OutOfDateDocuments() to check all documents in a namespace. You can use the various arguments to filter the documents that are checked (for example, to only check classes).
go to post Brett Saviano · Jan 29 Hi @Mathew Rimmington, thanks for following up with your solution! That is a creative way to solve the problem and I encourage you to submit your code as a Pull Request to the vscode-objectscript extension. It is a community tool so we would happy to include your code if it improves your experience. The contributing guide can be found here.
go to post Brett Saviano · Jan 25 Hi @Mathew Rimmington, this exact question was asked in a GitHub discussion a few weeks ago. To summarize my answer there, this isn't easy to add because the text that gets added on enter (besides indentation) is static. It acn't be generated from the regular expression used to match the previous line, so I couldn't dynamically add the correct number of dots. My recommendation is to use modern brace syntax instead of legacy dot syntax.
go to post Brett Saviano · Jan 24 @Nicki Vallentgoed You can convert the HttpResponse.Data into a %DynamicObject without using an intermediate stream: Set jsonob = ##class(%DynamicObject).%FromJSON(httprequest.HttpResponse.Data)
go to post Brett Saviano · Jan 23 @Evgeny Shvarov You can't use macros in a terminal so that's probably the cause.
go to post Brett Saviano · Jan 19 @Joseph Griffen ZWrite is going to output the internal format of the %Status value, which isn't that easy to parse visually. $SYSTEM.Status.DisplayError() will output the status text to the current device in a more readable format. USER>Write ##class(%Atelier.v1.Utils.General).ValidateDocName("project.prj",.sc) 0 USER>ZWrite sc sc="0 "_$lb($lb(16006,"project.prj",,,,,,,,$lb(,"USER",$lb("e^ValidateDocName+33^%apiSRC^2","e^ValidateDocName+1^%Atelier.v1.Utils.General.1^1","e^^^0"))))/* ERROR #16006: Document 'project.prj' name is invalid [ValidateDocName+33^%apiSRC:USER] */ USER>Do $SYSTEM.Status.DisplayError(sc) ERROR #16006: Document 'project.prj' name is invalid [ValidateDocName+33^%apiSRC:USER] If you need to store the status text in a variable you can use $SYSTEM.Status.GetErrorText().
go to post Brett Saviano · Jan 19 The list of supported file systems for your version (2023.1) can be found here.
go to post Brett Saviano · Jan 18 Sorry, I see that now! Have you checked your server connection information and made sure you have the correct host, port username and password?
go to post Brett Saviano · Jan 18 @Nimisha Joseph If you uninstalled Ensembe, what server are you trying to connect to?
