View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0004127Compliance Test Tool (CTT) Unified Architecture1 - Script Issuepublic2018-01-11 19:252019-08-07 12:07
ReporterBernd Edlinger Assigned ToAlexander Allmendinger  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
PlatformPCOSWindowsOS Version8.1
Product Version1.03.340.380 
Target Version1.03Fixed in Version1.03.341.381 
Summary0004127: Script error in Monitor Value Change/036.js
Description

This happens when no arrays are configured:

Test.Execute() encounted an unexpected error: TypeError: Result of expression near '...tampsToReturn.Both )[0]...' [null]
is not an object.
function:
file: C:/temp/CTT_1.3.340.378/NanoServer/library/Base/safeInvoke.js
line: 106
function:
file: C:/temp/CTT_1.3.340.378/NanoServer/maintree/Monitored Item Services/Monitor Value Change/Test Cases/036.js
line: 92

TagsNo tags attached.
Files Affected

Relationships

has duplicate 0004341 closedAlexander Allmendinger Monitored Item Services Monitor Value Change initialize.js 
has duplicate 0004743 closedPaul Hunkar Script error in Monitor Value Change/036.js 
related to 0004128 closedAlexander Allmendinger Error in Monitor Value Change/initialize.js 

Activities

Bernd Edlinger

2018-01-25 17:26

reporter   ~0008849

When an array is configured the script tries to
write a shorter value, but the server does not support
changing array sizes.
The write request Fails with BadTypeMismatch.
The script should be skipped, and not fail if that happens.

Alexander Allmendinger

2018-08-04 21:26

developer   ~0009260

The script should already skip itself if no arrays are configured. I modified the preparation in the initialize script to ensure the array items are surely set to null or are undefined. This should prevent the problem.

Paul Hunkar

2019-04-26 14:42

administrator   ~0010221

appears to still be an issue

Alexander Allmendinger

2019-08-01 15:09

developer   ~0010655

We ran the script during our CMP Call when reviewing MantisIssues and we weren't able to identify an issue when arrays are not configured.
The only thing happening then is that the script is printing a skipped message saying "Array Nodes not defined …".
Therefore we can't reproduce the problem in the current beta.

Paul Hunkar

2019-08-07 12:07

administrator   ~0010714

reviewed in CMP Call (8/1/2019)

Issue History

Date Modified Username Field Change
2018-01-11 19:25 Bernd Edlinger New Issue
2018-01-25 17:26 Bernd Edlinger Note Added: 0008849
2018-04-27 14:47 Paul Hunkar Assigned To => Alexander Allmendinger
2018-04-27 14:47 Paul Hunkar Status new => assigned
2018-08-04 21:26 Alexander Allmendinger Note Added: 0009260
2018-08-04 21:26 Alexander Allmendinger Status assigned => resolved
2018-08-04 21:26 Alexander Allmendinger Fixed in Version => 1.03.341.381
2018-08-04 21:26 Alexander Allmendinger Resolution open => fixed
2018-08-05 19:11 Alexander Allmendinger Relationship added related to 0004128
2018-10-02 14:02 Alexander Allmendinger Relationship added has duplicate 0004341
2019-01-28 14:10 Paul Hunkar Category Script Issue => 1 - Script Issue
2019-04-26 14:42 Paul Hunkar Status resolved => feedback
2019-04-26 14:42 Paul Hunkar Resolution fixed => reopened
2019-04-26 14:42 Paul Hunkar Note Added: 0010221
2019-04-26 14:42 Paul Hunkar Status feedback => assigned
2019-04-26 14:43 Paul Hunkar Relationship added related to 0004743
2019-04-26 14:44 Paul Hunkar Relationship replaced has duplicate 0004743
2019-08-01 15:09 Alexander Allmendinger Status assigned => resolved
2019-08-01 15:09 Alexander Allmendinger Resolution reopened => fixed
2019-08-01 15:09 Alexander Allmendinger Note Added: 0010655
2019-08-07 12:06 Paul Hunkar Target Version => 1.03
2019-08-07 12:07 Paul Hunkar Status resolved => closed
2019-08-07 12:07 Paul Hunkar Note Added: 0010714