How to fix Tosca script? Loginfo says Buffer with name 'WaitTime_S' was not found. What could be the issue and how to fix? - tosca

I am new to Tosca tool. There are some scripts already created earlier.
While running Template Instance, Error in loginfo says "Buffer with name 'WaitTime_S' was not found" and script failed.

In Tosca a Buffer is a value that has been set at a previous point in time either dynamically or statically.
Most likely your TestCase requires a Buffer to be set in a previous step or manually.
More information on Buffers can be found in the Tosca documentation

Related

Sagemaker Pipeline Error: Failed to upload to jumpstart-cache-prod-ap-southeast-1/source-directory-tarballs/lightgbm/inference/classification

I encountered this error when running pipeline.upsert()
S3UploadFailedError: Failed to upload /tmp/tmpexrxqr32/new.tar.gz to jumpstart-cache-prod-ap-southeast-1/source-directory-tarballs/lightgbm/inference/classification/v1.1.2/sourcedir.tar.gz: An error occurred (AccessDenied) when calling the CreateMultipartUpload operation: Access Denied
My pipeline consists of preprocessing, training, evaluating, creating model and transforming step. When i ran these steps seprarately they were working just fine, but when I put them together in a pipeline, the mentioned error occured. Can anyone tell me what is the cause of this error, I did not write any line of code to upload anything to Jumpstart S3.
model = Model(
image_uri=infer_image_uri,
model_data=step_train.properties.ModelArtifacts.S3ModelArtifacts,
sagemaker_session=pipeline_session,
role=role,
source_dir=infer_source_uri,
entry_point="inference.py"
)
When I comment out the entry_point line, pipeline.upsert() returned no error, but the transform job failed. The model I'm using is JumpStart LightGBM.
Nature of the problem
This happens by default because your experiment tries to upload the source code into its default bucket (which is the jumpstart bucket).
You can check the default bucket assigned to pipeline_session by printing pipeline_session.default_bucket().
Evidently you do not have the correct write permissions on that bucket and I encourage you to check them.
When you comment the entry_point, it doesn't give you that error precisely because it doesn't have anything to load. However, the moment it tries to do inference, it does not find the script clearly.
One possible quick and controllable solution
If you want to apply a cheat to verify what I told you, try putting the code_location parameter in the Model.
This way you can control exactly where your pipeline step goes to write. You will clearly need to specify the s3 uri of the desired destination folder.
code_location (str) – Name of the S3 bucket where custom code is
uploaded (default: None). If not specified, the default bucket created
by sagemaker.session.Session is used.

Unable to see the Buffer viewer list values in Tosca

I had ran my script and unable to see the buffer values in Buffer viewer. Can anyone please suggest if there is any settings to be changes
Ran my script to check for buffer values, but when i open the buffer viewer i dont see anything in the list but my script has passed successfully

Commands are not recorded on the SIM7080G GSM modem

I'm trying to figure out the SIM7080G module. An error occurs with some queries. To see the error code, send the command AT+CMEE = 1.
The problem is that I send this command and I get the answer OK. Next, I check if the value was written and see that it remains the same, equal to “0”.
Some commands have the same behavior. For example, with the command AT + CNMP = 13 I want to select the operating mode “GSM”, but the value remains equal to 38 - “LTE”.
But for example, with the command AT + IPR = 115200 I change the baudrate and it is correctly set.
Please tell me what could be the reason.
Thanks in advance.
A reboot probably occurred between the set command and the subsequent read command.
Commands parameters can be designed with three different behaviors:
Never saved after reboot
Always saved after reboot
Saved in a specific profile section (this is usually the case for ETSI standard commands)
Apparently SIM7080G module don't support profile sections. Anyway, for every command, "Parameter Saving Mode" is specified in the AT command guide.
The options are:
NO_SAVE: never saved through reboot.
AUTO_SAVE: The parameter of the current AT command is saved in NVRAM
automatically, it takes effect immediately, and it won't be lost if module is rebooted.
AUTO_SAVE_REBOOT: The parameter of the current AT command is saved in NVRAM
automatically, it takes effect immediately, and it won't be lost if module is rebooted.
-: "-" this AT command doesn’t care the parameter saving mode

Tosca - Java Exception while running Swing Application (JTree)

I am learning tosca and currently we are trying to run a regression test suite for a legacy Java Swing application.
My Test suite contains 4 modules (in JTree) and it is getting failed while clicking a node.
The Error I received on the module is,
at.tosca.javaengine.common.exceptions.ControlException: node or
node-path not found! Detailed information contained in
'JavaEngineException.txt above message is displayed in Executionlist
JavaEngineException.txt
22-11-2017 - 17:56:37: IExecWrapperInterface_connectToControl
at.tosca.javaengine.common.exceptions.ControlNotFoundException: Unable
to find control Index=3;ClassName(s)=[javax.swing.JTable];.
at.tosca.javaengine.server.tree.ComponentSearch.getComponent(ComponentSearch.java:218)
->at.tosca.javaengine.server.AbstractJavaEngineCore.findComponent(AbstractJavaEngineCore.java:1129)
->at.tosca.javaengine.server.AbstractJavaEngineCore.connectToControlInternal(AbstractJavaEngineCore.java:936)
->at.tosca.javaengine.server.AbstractJavaEngineCore.connectToControlInternal(AbstractJavaEngineCore.java:922)
->at.tosca.javaengine.server.AbstractJavaEngineCore.connectToControl(AbstractJavaEngineCore.java:313)
->at.tosca.javaengine.server.JavaEngineCore.access$101(JavaEngineCore.java:25)
->at.tosca.javaengine.server.JavaEngineCore$2.runInternal(JavaEngineCore.java:69)
->at.tosca.javaengine.server.control.WorkerThread.run(WorkerThread.java:69)
->java.lang.Thread.run(Unknown Source)
->JNIServer::CallVoidMethod
->CJNIServer::CallVoidMethod
22-11-2017 - 17:58:58: IExecWrapperInterface_setValue
at.tosca.javaengine.common.exceptions.ControlException: node or
node-path not found!
at.tosca.javaengine.server.control.swing.GenericTreeControl.setValueLegacy(GenericTreeControl.java:339)
->at.tosca.javaengine.server.control.swing.GenericTreeControl.setValue(GenericTreeControl.java:88)
->at.tosca.javaengine.server.AbstractJavaEngineCore.setValueInternal(AbstractJavaEngineCore.java:1195)
->at.tosca.javaengine.server.AbstractJavaEngineCore.setValue(AbstractJavaEngineCore.java:686)
->at.tosca.javaengine.server.JavaEngineCore.access$401(JavaEngineCore.java:25)
->at.tosca.javaengine.server.JavaEngineCore$5.runInternal(JavaEngineCore.java:114)
->at.tosca.javaengine.server.control.WorkerThread.run(WorkerThread.java:69)
->java.lang.Thread.run(Unknown Source)
->JNIServer::CallVoidMethod
->CJNIServer::CallVoidMethod
NOTE : The same Test suite is working in some other machine and not here. Both are same operating System.
This is a bit confusing.
Looks like you are connecting to a JTable and then trying to select a node? Are you sure Tosca is finding the correct control on both machines? (Index=3 does not sound like a stable identification.
The problem was TOSCA is faster than our application :)
Meaning: The frame was not loaded at the time when TOSCA was trying to scan the next page causing the error, the specific node was
not found.
Solution: I added a TBoxWait with extra seconds, after that this is working fine.

Error while saving data to data table in Pega PRPC

While saving data in Pega PRPC using activity with Obj-save method, I got following error message:
pyCommitError: A commit cannot be performed because a deferred save of instance ANDY-FW-ANDYCARRENTALFW-DATA-CARINFO L3 failed: code: SQLState: Message:
Can anyone share some idea on how to fix this issue?
Andy
This message could come when we have a field which has a less field length specified in DB and we are trying to insert bigger string in the field.
There could be other reasons as well.See Tracer.
Deferred save of instance usually fails due to locked instance which you are trying to commit. Or the record you are trying to commit is stale (someone else committed before your commit)
Ideally, this behavior can be observed because of the lock on the work object not being held while you are trying to save the object. Make sure you acquire the lock before updating and save.
Additionally please check if privilege is given to the operator.

Resources