Search

Hello,I tested the query on the Config.ConfigFile table of the Namespace %SYS, it returned 3 lines and a fatal error: SELECT * FROM Config.ConfigFile I tested the same query

: // Create a Role %SYS>Set status = ##class(Security.Roles).Create("testRole","a test Role","%Development:U,%DB_USER:R") // Creation was successful %SYS>Write

-from-huggingface) - [5.2.1. Settings](#521-settings) - [5.2.2. Testing](#522-testing) - [6. Fine-tune the models](#6-fine-tune-the-models) - [6.1. Tunning the model

, where you can easily define also user and password for external use. Running server $ docker run -d --rm --name iris \ -p 52773:52773 \ -e IRIS_USER=test \ -e

description given below, we would like you to beta test the exam. The dates the exam will be available for beta testing are March 28 - April 30, 2023. Interested beta testers should

and not a string, as discussed here...https://community.intersystems.com/post/compilation-gotchas-and-request-changeA second approach is to use Unit Testing to ensure not only

be adjusted to call the method via the class/object. Details Prior to IRIS 2023.1 when you compiled a class User.Test.cls with a method such as: method Test() { Write "Test

on your workstation, nor will any settings have to be changed on it. To take Serenji for a test drive please visit https://georgejames.com/dc-gitpod Looking forward to testing

way is to run the workload and see how much journals are generated. Otherwise run workload tests in a DEV environment. The more write-intensive the system is the more journals

a TransactionObject whith working versions... Hi Stefan. That shouldn't happen. Could you share test code that shows the problem? Hi Raj, on writing test code for you i noticed that this might

Hi, I am facing an issue after upgrading from Ensemble version 2015.1 to 2017.1. On 2015.1, I was testing a Rest operation using a https mock-server. But now on 2017.1

. Without a timeout, a process can hang indefinitely due to a lock. You could argue its good practice to use a timeout. If you implement a timeout, always verify the value of $test

test the exam. We anticipate the exam being available for beta testing on February 7, 2022, but interested beta testers should sign up now by emailing certification

, testing it in batch on other test data and invoking it from code, as you would do in a regular application or as part of a business process.PrerequisitesYou should have experience