titan.EclipsePlug-ins issueshttps://gitlab.eclipse.org/eclipse/titan/titan.EclipsePlug-ins/-/issues2023-06-09T10:09:58Zhttps://gitlab.eclipse.org/eclipse/titan/titan.EclipsePlug-ins/-/issues/511Error markers are shown after editing with earlier code content2023-06-09T10:09:58ZEduárd CzimbalmosError markers are shown after editing with earlier code content## Summary
After correcting an erroneous code, Eclipse TITAN Designer still shows error marker with the earlier code content.
## Steps and/or TTCN-3 code to reproduce
Happens on big project, could not reproduce it with small project. ...## Summary
After correcting an erroneous code, Eclipse TITAN Designer still shows error marker with the earlier code content.
## Steps and/or TTCN-3 code to reproduce
Happens on big project, could not reproduce it with small project. I've shown it to @aknappqwt on screen share.
## Platform details (OS type and version)
eclipse.buildId=4.27.0.20230309-1200
eclipse.vm=/home/ethecs/.p2/pool/plugins/org.eclipse.justj.openjdk.hotspot.jre.full.linux.x86_64_17.0.2.v20220201-1208/jre/bin/java
Ubuntu 22.04
/cc @aknappqwt @mmagyarihttps://gitlab.eclipse.org/eclipse/titan/titan.EclipsePlug-ins/-/issues/502Document comment lexer/parser error handling2022-11-08T09:06:12ZMiklos MagyariDocument comment lexer/parser error handlingDocument comment lexer/parser should do a better job for error handling.
Example:
If a html tag is used when only an identifier is expected, an antlr error is printed instead of a graceful error handling.
Code to reproduce:
`//* @verd...Document comment lexer/parser should do a better job for error handling.
Example:
If a html tag is used when only an identifier is expected, an antlr error is printed instead of a graceful error handling.
Code to reproduce:
`//* @verdict <b>fail</b>`Miklos MagyariMiklos Magyarihttps://gitlab.eclipse.org/eclipse/titan/titan.EclipsePlug-ins/-/issues/494Titanium searching for port and component instances in the wrong scope2022-07-27T07:26:52ZLevente ErősTitanium searching for port and component instances in the wrong scope## Summary
Component and port references are searched for on module level.
## Steps and/or TTCN-3 code to reproduce
```
module connections {
type integer myint;
type port pt1 message{
inout integer
}with{extension "internal"}
typ...## Summary
Component and port references are searched for on module level.
## Steps and/or TTCN-3 code to reproduce
```
module connections {
type integer myint;
type port pt1 message{
inout integer
}with{extension "internal"}
type port pt2 message{
inout myint
}with{extension "internal"}
type component parent{
port pt1 P1;
port pt2 P2;
}
function receiver() runs on parent{
P2.receive;
}
testcase tc_pt_compatibility() runs on parent{
var parent ptc := parent.create;
connect(mtc:P1, ptc:P2);
ptc.start(receiver());
P1.send(1);
}
}
```
## What is the current bug behavior?
The ptc.start(receiver()); line gets an error saying there is no definition named ptc
P1.send(1); gets an error saying there is no definition named ptc
However, the code compiles and runs.
## What is the expected correct behavior?
Neither of these should be problems as ptc is defined on testcase level, while P1 in the scope of the component that the testcase runs on.
## Relevant logs and/or screenshots
## Possible fixes
## Titan version
8.1.0
## Platform details (OS type and version)
Microsoft Windows 10 Enterprise 10.0.19042
/cc @aknappqwtMiklos MagyariMiklos Magyarihttps://gitlab.eclipse.org/eclipse/titan/titan.EclipsePlug-ins/-/issues/456TITAN is reporting warnings and errors on publicly available 3GPP test suites...2021-12-26T09:37:05ZKristof SzabadosTITAN is reporting warnings and errors on publicly available 3GPP test suites on ttcn-3.org## Summary
For a research article, we tried to do measurements with TITAN on publicly available official TTCN-3 test suites from www.ttcn-3.org
For this, we used the 3GPP Test suites. As they seem to be related to currently very importa...## Summary
For a research article, we tried to do measurements with TITAN on publicly available official TTCN-3 test suites from www.ttcn-3.org
For this, we used the 3GPP Test suites. As they seem to be related to currently very important 5G technology they should have the best support. Also, they looked to be the largest official and standardized projects, which is beneficial for our measurements.
## Steps and/or TTCN-3 code to reproduce
1) Download the zip file of the project
2) create a project for it in Eclipse for TITAN to handle.
3) Convert the xsd files in the project into .ttcn files using TITAN's converter using the -N flag to make sure that all definitions of the XML Schemas with no target namespaces are generated into different TTCN-3 modules.
## What is the current bug behavior?
TITAN reports warnings and errors for every project.
For many of them, TITAN also reports unsupported elements and syntactical problems.
34123-3-g20 (SSNITZ) 11 warnings 249 errors //2 syntactic problems, 8 warnings for not supported elements
34123-3-g20 (UTRAN) 10 warnings 278 errors //3 syntactic problems, 3 warnings for not supported elements
34229-3-g20 (IMS_EUTRA) 22 warnings 70 errors //5 syntactic problems
34229-3-g20 (IMS_IRAT) 21 warnings 226 errors //4 syntactic problems, 3 warnings for not supported elements
34229-3-g20 (IMS_NR5GC) 42 warnings 52 errors //3 syntactic problems, 1 warning for not supported elements
34229-3-g20 (IMS_UTRAN) 10 warnings 266 errors //3 syntactic problems, 2 warnings for not supported elements
34229-3-g20 (IMS_WLAN) 14 warnings 62 errors //2 syntactic problems
36523-3-g90 (LTE) 25 warnings 62 errors //4 syntactic problems, 3 warnings for not supported elements
36523-3-g90 (LTE_A_IRAT)24 warnings 234 errors //4 syntactic problems, 3 warnings for not supported elements
36523-3-g90 (LTE_IRAT) 24 warnings 248 errors //4 syntactic problems, 3 warnings for not supported elements
38523-3-g20 (ENDC) 40 warnings 53 errors //8 syntactic problems (4 errors), 2 warning for not supported elements
38523-3-g20 (NR5GC) 67 warnings 54 errors //3 syntactic problems, 1 warning for not supported elements
38523-3-g20 (NR5GC_IRAT)55 warnings 62 errors //8 syntactic problems (4 errors), 2 warning for not supported elements
Please note, that for some of these projects the semantic analysis of TITAN also sometimes throws exceptions.
Luckily for our measurements, this is not happening every time, but should be investigated.
To reproduce you need to open + close a given project several times (this is the method we used for our measurements).
The exception(s) should be found in the error log view of Eclipse after a few dozen iterations.
## What is the expected correct behavior?
As these are the official publicly available and standardized test suites of 3GPP (and probably ETSI) testing the functionalities of 5G and other very important protocols ... it would be preferable if they would be supported by TITAN.
Without the need to change them manually to remove all of the warnings/errors ... as having to modify official tests manually to make sure they can be used raises suspicion related to whether the equipment being tested would really pass the official tests or only hand modified ones.
## Relevant logs and/or screenshots
## Possible fixes
## Titan version
8.0.0
## Platform details (OS type and version)
Windows 10
(our observations and measurements were done a few months ago, but on a fully updated operating system at that time)
/cc @aknappqwthttps://gitlab.eclipse.org/eclipse/titan/titan.EclipsePlug-ins/-/issues/422First build of a freshly cloned repo fails with antlr problems2021-06-25T10:57:34ZMiklos MagyariFirst build of a freshly cloned repo fails with antlr problemsHow to reproduce:
1. clone a fresh copy of the repo
2. import it to a clean workspace in eclipse
3. build
The build fails (see below). Most probably we need to revise the order of the build of the g4 files to fix this.
All the later bu...How to reproduce:
1. clone a fresh copy of the repo
2. import it to a clean workspace in eclipse
3. build
The build fails (see below). Most probably we need to revise the order of the build of the g4 files to fix this.
All the later builds work, as the .tokens files are generated by the first one and not deleted by clean.
```
ANTLR Tool v4.3 (C:\Users\GezaBela\antlr\antlr-4.3-complete.jar)
CfgParser.g4 -o C:\Users\GezaBela\Source\Repos\gitlab\master\org.eclipse.titan.common\src\org\eclipse\titan\common\parsers\cfg -no-listener -no-visitor -package org.eclipse.titan.common.parsers.cfg -encoding UTF-8
error(3): cannot find tokens file 'CfgLexer.tokens'
warning(125): CfgParser.g4:364:0: implicit definition of token 'MAIN_CONTROLLER_SECTION' in parser
warning(125): CfgParser.g4:365:24: implicit definition of token 'SEMICOLON' in parser
warning(125): CfgParser.g4:379:1: implicit definition of token 'UNIXSOCKETS' in parser
warning(125): CfgParser.g4:380:1: implicit definition of token 'ASSIGNMENTCHAR' in parser
warning(125): CfgParser.g4:392:2: implicit definition of token 'YES' in parser
warning(125): CfgParser.g4:392:8: implicit definition of token 'NO' in parser
warning(125): CfgParser.g4:396:1: implicit definition of token 'KILLTIMER' in parser
warning(125): CfgParser.g4:409:1: implicit definition of token 'LOCALADDRESS' in parser
warning(125): CfgParser.g4:420:1: implicit definition of token 'NUMHCS' in parser
warning(125): CfgParser.g4:433:1: implicit definition of token 'TCPPORT' in parser
warning(125): CfgParser.g4:446:1: implicit definition of token 'INCLUDE_SECTION' in parser
```
(...many more lines omitted...)Miklos MagyariMiklos Magyarihttps://gitlab.eclipse.org/eclipse/titan/titan.EclipsePlug-ins/-/issues/389Invalid error marker for port arrays in log2str2021-06-07T15:09:59ZEclipse WebmasterInvalid error marker for port arrays in log2str## Submitted by Anton Vikstrom
**[Link to original bug (#569624)](https://bugs.eclipse.org/bugs/xmlrpc.cgishow_bug.cgi?id=569624)**
## Description
Titan Designer plug-in (version "7/CAX 105 7730 R2A (7.2.pl0)", but this page would n...## Submitted by Anton Vikstrom
**[Link to original bug (#569624)](https://bugs.eclipse.org/bugs/xmlrpc.cgishow_bug.cgi?id=569624)**
## Description
Titan Designer plug-in (version "7/CAX 105 7730 R2A (7.2.pl0)", but this page would not allow me to select higher than 7.1.0) shows an invalid error marker:
“Refence to a value or template was expected instead of port”
when a port array is used in log2str. Titan transforms this without problem to a string so that port name can be used in the log, so this code is valid.
Minimal example:
~~~
import from IPL4asp_PortType all;
type component Minimal_CT
{
port IPL4asp_PT array_PT[1]
port IPL4asp_PT single_PT
}
testcase tc_log_port()
runs on Minimal_CT
{
setverdict(pass);
// No error markers:
log(single_PT);
log(log2str("Port named :", single_PT));
var charstring vl_logstring_1 := log2str("Port named :", single_PT);
// Error markers on all:
log(array_PT[0]);
log(log2str("Port named :", array_PT[0]));
var charstring vl_logstring_2 := log2str("Port named :", array_PT[0]);
}
~~~
Version: 7.1.0Miklos MagyariMiklos Magyarihttps://gitlab.eclipse.org/eclipse/titan/titan.EclipsePlug-ins/-/issues/345jump to definition issue in for loops2021-05-06T14:58:05ZEclipse Webmasterjump to definition issue in for loops## Submitted by Kristof Szabados
**[Link to original bug (#564280)](https://bugs.eclipse.org/bugs/xmlrpc.cgishow_bug.cgi?id=564280)**
## Description
When incremental parsing is enabled jump to definition might jump slightly off targ...## Submitted by Kristof Szabados
**[Link to original bug (#564280)](https://bugs.eclipse.org/bugs/xmlrpc.cgishow_bug.cgi?id=564280)**
## Description
When incremental parsing is enabled jump to definition might jump slightly off target for for loop definitions.
Example code:
~~~
for (var integer j := 0; j < loopcounter2; j := j + 1) {
var integer y := j;
}
~~~
If we press space somewhere before the loop, place the cursor behind "j" in the variable definition and press F3, the cursor will jump on the character before the 'j' in the variable definition.
Version: 6.6.1https://gitlab.eclipse.org/eclipse/titan/titan.EclipsePlug-ins/-/issues/338Big unicode characters in TitanUniversalCharString2021-05-06T14:53:23ZEclipse WebmasterBig unicode characters in TitanUniversalCharString## Submitted by Arpad Lovassy
Assigned to **Arpad Lovassy**
**[Link to original bug (#561795)](https://bugs.eclipse.org/bugs/xmlrpc.cgishow_bug.cgi?id=561795)**
## Description
In Java the biggest unicode codepoint is 10FFFF, while...## Submitted by Arpad Lovassy
Assigned to **Arpad Lovassy**
**[Link to original bug (#561795)](https://bugs.eclipse.org/bugs/xmlrpc.cgishow_bug.cgi?id=561795)**
## Description
In Java the biggest unicode codepoint is 10FFFF, while in TTCN-3 the biggest universal charstring is (FF,FF,FF,FF), so unicode characters above 10FFFF must be treated differentlyhttps://gitlab.eclipse.org/eclipse/titan/titan.EclipsePlug-ins/-/issues/334Semantic analyzer: false error message on encvalue(x,"","JSON") where x is BI...2021-05-06T14:51:19ZEclipse WebmasterSemantic analyzer: false error message on encvalue(x,"","JSON") where x is BIT STRING## Submitted by Jeno Attila Balasko
Assigned to **Arpad Lovassy**
**[Link to original bug (#560028)](https://bugs.eclipse.org/bugs/xmlrpc.cgishow_bug.cgi?id=560028)**
## Description
Created attachment 281780
JsonBasicASN1EncDecTes...## Submitted by Jeno Attila Balasko
Assigned to **Arpad Lovassy**
**[Link to original bug (#560028)](https://bugs.eclipse.org/bugs/xmlrpc.cgishow_bug.cgi?id=560028)**
## Description
Created attachment 281780
JsonBasicASN1EncDecTest1.ttcn
If there is an asn1 type definition:
`Asn1-bs ::= BIT STRING`
and it is used in a ttcn module:
~~~
testcase tc_asn1_bs2bs_bug() runs on CT {
var Asn1_bs x := '01'B, d;
var bitstring encoded2 := encvalue(x, "", "JSON");
var bitstring expected := '0010 0010 00110000 00110001 0010 0010'B;// "01"
f_compare_bitstring(encoded2,expected);
}
type component CT {}
~~~
then the line with `encode()` is marked with this semantic error marker:
No coding rule specified for type `bitstring' JsonBasicASN1EncDecTest1.ttcn /TR_2019_12_ttcn2cpp/src line 73 on-the-fly semantic markers
Remark: The code can be compiled for cpp and run with success. Code attached.
**Attachment 281780**, "JsonBasicASN1EncDecTest1.ttcn":
[JsonBasicASN1EncDecTest1.ttcn](/uploads/478b975240832eb20bfb551d150f1666/JsonBasicASN1EncDecTest1.ttcn)
Version: 6.6.1https://gitlab.eclipse.org/eclipse/titan/titan.EclipsePlug-ins/-/issues/332ASN.1 false semantic error on generated information object type "oneErrorObje...2021-05-06T14:48:05ZEclipse WebmasterASN.1 false semantic error on generated information object type "oneErrorObject-Type"## Submitted by Jeno Attila Balasko
**[Link to original bug (#560000)](https://bugs.eclipse.org/bugs/xmlrpc.cgishow_bug.cgi?id=560000)**
## Description
Created attachment 281768
Example: X682.asn
This TR is in close connection with...## Submitted by Jeno Attila Balasko
**[Link to original bug (#560000)](https://bugs.eclipse.org/bugs/xmlrpc.cgishow_bug.cgi?id=560000)**
## Description
Created attachment 281768
Example: X682.asn
This TR is in close connection with titan.core [bug 528313](https://bugs.eclipse.org/bugs/xmlrpc.cgishow_bug.cgi?id=528313) which is corrected in 2017.
In the attached file, the commented line "errorInfo oneErrorObject-Type : foobar" has a semantic marker as follows:
Reference to a non-existent alternative `oneErrorObject-Type' in CHOICE value for type `@X682.ErrorReturn.errors.oftype.errorInfo[1]' X682.asn /Regression_Test_java/src/EncodeDecode/BER line 80 on-the-fly semantic markers
The reason is that the semantic analyzer does not take into account that the oneErrorObject name will be changed into oneErrorObject-Type (see also the cpp compiler log).
### ASN1.code detail:
~~~
ERROR-CLASS ::= CLASS
{
&category PrintableString(SIZE(1)),
&code INTEGER,
&Type DEFAULT INTEGER
}
WITH SYNTAX {&category &code [&Type]}
ErrorSet ERROR-CLASS ::=
{
{"A" 1 [1] INTEGER} |
{"A" 2 [1] VisibleString} |
{"B" 1 [1] PrintableString} |
{"B" 2 [1] BOOLEAN} |
oneErrorObject
}
oneErrorObject ERROR-CLASS ::= { "C" 3 ENUMERATED{foobar} }
ErrorReturn ::= SEQUENCE
{
errorCategory ERROR-CLASS.&category ({ErrorSet}) OPTIONAL,
errors SEQUENCE OF SEQUENCE
{
errorCode ERROR-CLASS.&code({ErrorSet}{@errorCategory}),
errorInfo [99] ERROR-CLASS.&Type({ErrorSet}{@errorCategory,@.errorCode}) -- line 51
} OPTIONAL
}
...
errorReturn2 ErrorReturn ::=
{
errorCategory "3",
errors
{
{
errorCode 3,
errorInfo oneErrorObject-Type : foobar --error marker on this line
}
}
}
~~~
### Remark:
Perhaps the cpp compilation log helps:
~~~
../src/X682.asn: In ASN.1 module `X682':
../src/X682.asn:45: In type assignment `ErrorReturn':
../src/X682.asn:51: In constraint #1 of type `open type':
../src/X682.asn:51: warning: Strange alternative name (`errorSet-1-Type') was added to open type `@X682.ErrorReturn.errors.SEQUENCE.errorInfo.type'
../src/X682.asn:51: warning: Strange alternative name (`errorSet-2-Type') was added to open type `@X682.ErrorReturn.errors.SEQUENCE.errorInfo.type'
../src/X682.asn:51: warning: Strange alternative name (`errorSet-3-Type') was added to open type `@X682.ErrorReturn.errors.SEQUENCE.errorInfo.type'
../src/X682.asn:51: warning: Strange alternative name (`errorSet-4-Type') was added to open type `@X682.ErrorReturn.errors.SEQUENCE.errorInfo.type'
../src/X682.asn:51: warning: Strange alternative name (`oneErrorObject-Type') was added to open type `@X682.ErrorReturn.errors.SEQUENCE.errorInfo.type'
~~~
**Attachment 281768**, "Example: X682.asn":
[X682.asn](/uploads/bda871990d2884661af685c64709ebc5/X682.asn)
Version: 6.6.1https://gitlab.eclipse.org/eclipse/titan/titan.EclipsePlug-ins/-/issues/330Semantic analyzer puts false error markers "Reference to a non-existent field...2021-05-06T14:44:55ZEclipse WebmasterSemantic analyzer puts false error markers "Reference to a non-existent field" onto an open type value## Submitted by Jeno Attila Balasko
**[Link to original bug (#559832)](https://bugs.eclipse.org/bugs/xmlrpc.cgishow_bug.cgi?id=559832)**
## Description
Created attachment 281700
JSonData.asn : the first example file (data)
The sema...## Submitted by Jeno Attila Balasko
**[Link to original bug (#559832)](https://bugs.eclipse.org/bugs/xmlrpc.cgishow_bug.cgi?id=559832)**
## Description
Created attachment 281700
JSonData.asn : the first example file (data)
The semantic analyser of the titan eclipse plugin puts two error markers on the file OpenTypeBug.ttcn, altought the files can be compiled successfully by the cpp code generator.
The markers:
Description Resource Path Location Type
Reference to a non-existent field `iNTEGER' in union value for type `@JsonData.ProtocolElem-Field.JsonData.inst1.val[1]' OpenTypeBug.ttcn /TR_2019_12_ttcn2cpp/src/ASN_OpentypeBug.ttcn line 26 on-the-fly semantic markers
Reference to a non-existent field `iA5String' in union value for type `@JsonData.ProtocolElem-Field.JsonData.inst1.val[1]' OpenTypeBug.ttcn /TR_2019_12_ttcn2cpp/src/ASN_OpentypeBug.ttcn line 27 on-the-fly semantic markers
**Attachment 281700**, "JSonData.asn : the first example file (data)":
[JsonData.asn](/uploads/144137bf650f39c5e7e14e2b14c3d1c4/JsonData.asn)
Version: 6.6.1https://gitlab.eclipse.org/eclipse/titan/titan.EclipsePlug-ins/-/issues/328Semantic analyzer: false error message " `omit' value is not allowed in this ...2021-05-06T14:43:49ZEclipse WebmasterSemantic analyzer: false error message " `omit' value is not allowed in this context"## Submitted by Jeno Attila Balasko
**[Link to original bug (#559750)](https://bugs.eclipse.org/bugs/xmlrpc.cgishow_bug.cgi?id=559750)**
## Description
Created attachment 281668
example ttcn source code (2nd file is required)
This ...## Submitted by Jeno Attila Balasko
**[Link to original bug (#559750)](https://bugs.eclipse.org/bugs/xmlrpc.cgishow_bug.cgi?id=559750)**
## Description
Created attachment 281668
example ttcn source code (2nd file is required)
This false error message arrived as an exception (under semantic analyzis):
!ENTRY org.eclipse.titan.common 4 0 2020-01-31 14:21:35.760
!MESSAGE INTERNAL_ERROR: The following semantic error was reported on a non-existent location: `omit' value is not allowed in this context
!STACK 0
java.lang.Exception: The following semantic error was reported on a non-existent location: `omit' value is not allowed in this context
at org.eclipse.titan.common.logging.ErrorReporter.INTERNAL_ERROR(ErrorReporter.java:68)
at org.eclipse.titan.designer.AST.NULL_Location.reportSemanticError(NULL_Location.java:42)
at org.eclipse.titan.designer.AST.Type.checkThisValue(Type.java:1455)
at org.eclipse.titan.designer.AST.TTCN3.types.OctetString_Type.checkThisValue(OctetString_Type.java:130)
at org.eclipse.titan.designer.AST.ASN1.types.ASN1_Sequence_Type.checkThisValueSeq_A(ASN1_Sequence_Type.java:803)
at org.eclipse.titan.designer.AST.ASN1.types.ASN1_Sequence_Type.checkThisValue(ASN1_Sequence_Type.java:540)
at org.eclipse.titan.designer.AST.TTCN3.types.Referenced_Type.checkThisValue(Referenced_Type.java:373)
at org.eclipse.titan.designer.AST.TTCN3.templates.SpecificValue_Template.checkExpressionSelfReferenceTemplate(SpecificValue_Template.java:270)
at org.eclipse.titan.designer.AST.TTCN3.values.expressions.MatchExpression.checkExpressionSelfReference(MatchExpression.java:65)
at org.eclipse.titan.designer.AST.Type.checkThisValue(Type.java:1479)
at org.eclipse.titan.designer.AST.TTCN3.types.Boolean_Type.checkThisValue(Boolean_Type.java:127)
at org.eclipse.titan.designer.AST.TTCN3.definitions.FormalParameter.checkActualParameterValue(FormalParameter.java:568)
at org.eclipse.titan.designer.AST.TTCN3.definitions.FormalParameter.checkActualParameter(FormalParameter.java:517)
at org.eclipse.titan.designer.AST.TTCN3.definitions.FormalParameterList.checkActualParameterList(FormalParameterList.java:709)
at org.eclipse.titan.designer.AST.TTCN3.definitions.FormalParameterList.checkActualParameterList(FormalParameterList.java:634)
at org.eclipse.titan.designer.AST.ParameterisedSubReference.checkParameters(ParameterisedSubReference.java:105)
at org.eclipse.titan.designer.AST.Reference.getRefdAssignment(Reference.java:536)
at org.eclipse.titan.designer.AST.Reference.getRefdAssignment(Reference.java:475)
at org.eclipse.titan.designer.AST.TTCN3.statements.Function_Instance_Statement.check(Function_Instance_Statement.java:103)
at org.eclipse.titan.designer.AST.TTCN3.statements.Unknown_Instance_Statement.check(Unknown_Instance_Statement.java:141)
at org.eclipse.titan.designer.AST.TTCN3.statements.StatementBlock.check(StatementBlock.java:614)
at org.eclipse.titan.designer.AST.TTCN3.definitions.Def_Testcase.check(Def_Testcase.java:300)
at org.eclipse.titan.designer.AST.TTCN3.definitions.Def_Testcase.check(Def_Testcase.java:236)
at org.eclipse.titan.designer.AST.TTCN3.definitions.Definitions.check(Definitions.java:446)
at org.eclipse.titan.designer.AST.TTCN3.definitions.TTCN3Module.check(TTCN3Module.java:482)
at org.eclipse.titan.designer.AST.brokenpartsanalyzers.BrokenPartsChecker.generalChecker(BrokenPartsChecker.java:187)
at org.eclipse.titan.designer.AST.brokenpartsanalyzers.BrokenPartsChecker.doChecking(BrokenPartsChecker.java:69)
at org.eclipse.titan.designer.parsers.ProjectSourceSemanticAnalyzer.analyzeMultipleProjectsSemantically(ProjectSourceSemanticAnalyzer.java:401)
at org.eclipse.titan.designer.parsers.ProjectSourceParser.internalDoAnalyzeWithReferences(ProjectSourceParser.java:782)
at org.eclipse.titan.designer.parsers.ProjectSourceParser.access$4(ProjectSourceParser.java:678)
at org.eclipse.titan.designer.parsers.ProjectSourceParser$10.runInWorkspace(ProjectSourceParser.java:985)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60)
**Attachment 281668**, "example ttcn source code (2nd file is required)":
[JsonDataAsn1OptionalBugTest.ttcn](/uploads/2a2c6863e847dd8d6edc81027625d302/JsonDataAsn1OptionalBugTest.ttcn)
Version: 6.6.1https://gitlab.eclipse.org/eclipse/titan/titan.EclipsePlug-ins/-/issues/322ttcn2java: wrong handling of permutation in case of compatible integer templa...2021-05-06T14:34:22ZEclipse Webmasterttcn2java: wrong handling of permutation in case of compatible integer template arrays## Submitted by Jeno Attila Balasko
**[Link to original bug (#559512)](https://bugs.eclipse.org/bugs/xmlrpc.cgishow_bug.cgi?id=559512)**
## Description
Created attachment 281594
example ttcn source code
The attached ttcn module con...## Submitted by Jeno Attila Balasko
**[Link to original bug (#559512)](https://bugs.eclipse.org/bugs/xmlrpc.cgishow_bug.cgi?id=559512)**
## Description
Created attachment 281594
example ttcn source code
The attached ttcn module contains two testcases. They are almost identical.
The first testcase creates a template variable with a permutation value, then calls a function with arg type of template AI3. The function simple checks if the received variable is the expected or not ( converted into string):
type integer AI3[3];
testcase tc_array_allfrom_perm1_pass() runs on CT {
//This testcase does not use type compatibility
var template AI3 tl_AI3 := { permutation(1,*,3) };
log( "TC() local var tl_tcAI3: ", tl_AI3);
f_check( tl_AI3);
}
The second testcase creates a template variable of type compatible with the previous AI3. The value is the same as in the first testcase. Then the same function is called. It fails because ( as we can see from the logs ) the information about the permutation is not passed.From the log it trivial that the value was correct before the function call but the converted value arrived without the "permutaion"info.
tl_integerArray3 before function call: { permutation(1, *, 3) }
Function arg:{ 1, *, 3 }
setverdict(fail): none -> fail reason: "Expected: { permutation(1, *, 3) }, got: "{ 1, *, 3 }"", new component reason: "Expected: { permutation(1, *, 3) }, got: "{ 1, *, 3 }""
Source code and log are attached
**Attachment 281594**, "example ttcn source code":
[permTemplateAsFuncArgBug.ttcn](/uploads/8340d96b2486de133643082fdbb932b3/permTemplateAsFuncArgBug.ttcn)
Version: 6.6.1https://gitlab.eclipse.org/eclipse/titan/titan.EclipsePlug-ins/-/issues/250Eclipse plugin should allow syntax of package specification2021-08-09T08:03:08ZEclipse WebmasterEclipse plugin should allow syntax of package specification## Submitted by Bence Janos Szabo
**[Link to original bug (#520969)](https://bugs.eclipse.org/bugs/xmlrpc.cgishow_bug.cgi?id=520969)**
## Description
Created attachment 269846
LanguageSpec.ttcn
See:
https://bugs.eclipse.org/bugs/s...## Submitted by Bence Janos Szabo
**[Link to original bug (#520969)](https://bugs.eclipse.org/bugs/xmlrpc.cgishow_bug.cgi?id=520969)**
## Description
Created attachment 269846
LanguageSpec.ttcn
See:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=515564
Testfiles attached
**Attachment 269846**, "LanguageSpec.ttcn":
[LanguageSpec.ttcn](/uploads/0f4fbb0739e45a2908fa06cbf3e83a59/LanguageSpec.ttcn)
Version: 6.2.0https://gitlab.eclipse.org/eclipse/titan/titan.EclipsePlug-ins/-/issues/232LogViewer unable to parse HelloWorld project log if DEBUG mask is enabled2021-05-06T13:13:16ZEclipse WebmasterLogViewer unable to parse HelloWorld project log if DEBUG mask is enabled## Submitted by fiannetti `@fiannetti`
Assigned to **Jeno Attila Balasko**
**[Link to original bug (#515559)](https://bugs.eclipse.org/bugs/xmlrpc.cgishow_bug.cgi?id=515559)**
## Description
LogViewer unable to parse HelloWorld pr...## Submitted by fiannetti `@fiannetti`
Assigned to **Jeno Attila Balasko**
**[Link to original bug (#515559)](https://bugs.eclipse.org/bugs/xmlrpc.cgishow_bug.cgi?id=515559)**
## Description
LogViewer unable to parse HelloWorld project log if DEBUG mask is enabled
The error message states that there's no MSC data for the log
Version: 6.1.0https://gitlab.eclipse.org/eclipse/titan/titan.EclipsePlug-ins/-/issues/213Test that eclipse plug in handles modified template restrictions well2021-05-06T11:20:33ZEclipse WebmasterTest that eclipse plug in handles modified template restrictions well## Submitted by Bence Janos Szabo
**[Link to original bug (#511771)](https://bugs.eclipse.org/bugs/xmlrpc.cgishow_bug.cgi?id=511771)**
## Description
All template restriction can be modified to all template restrictions when a templ...## Submitted by Bence Janos Szabo
**[Link to original bug (#511771)](https://bugs.eclipse.org/bugs/xmlrpc.cgishow_bug.cgi?id=511771)**
## Description
All template restriction can be modified to all template restrictions when a template modifies another.
See:titan.core/function_test/Semantic_Analyser/template/TempRes_OK.ttcn
Version: 6.1.0https://gitlab.eclipse.org/eclipse/titan/titan.EclipsePlug-ins/-/issues/209in the oneM2M tests there is a situation where fields of the anytype type are...2021-05-06T11:21:32ZEclipse Webmasterin the oneM2M tests there is a situation where fields of the anytype type are not recognised in the Designer## Submitted by Kristof Szabados
**[Link to original bug (#511384)](https://bugs.eclipse.org/bugs/xmlrpc.cgishow_bug.cgi?id=511384)**
## Description
After downloading the oneM2Mtester source codes I noticed a problem in anytype hand...## Submitted by Kristof Szabados
**[Link to original bug (#511384)](https://bugs.eclipse.org/bugs/xmlrpc.cgishow_bug.cgi?id=511384)**
## Description
After downloading the oneM2Mtester source codes I noticed a problem in anytype handling.
In some cases fields of the anytype were reported as missing or invalid.
oneM2Mtester can be found here: https://git.onem2m.org/TST/ATS/tree/master
Version: 6.1.0https://gitlab.eclipse.org/eclipse/titan/titan.EclipsePlug-ins/-/issues/139Open declaration sometimes does not work2021-05-06T10:39:44ZEclipse WebmasterOpen declaration sometimes does not work## Submitted by Kristof Szabados
**[Link to original bug (#497244)](https://bugs.eclipse.org/bugs/xmlrpc.cgishow_bug.cgi?id=497244)**
## Description
Sometimes the open declaration functionality does not work.
The only output on the ...## Submitted by Kristof Szabados
**[Link to original bug (#497244)](https://bugs.eclipse.org/bugs/xmlrpc.cgishow_bug.cgi?id=497244)**
## Description
Sometimes the open declaration functionality does not work.
The only output on the debug console is that, the module in the file could not be identified.
Can not be reproduced consistently, but some users have a higher likelyhood of experiencing this issue.
It might be interesting to mention, that opening a file from the search results window, seems to increase the likelyhood of the issue, compared to opening it from the navigator window.
And most of the time inserting and deleting a character can solve the issue for the actual file, but not always.
Version: 5.5.0https://gitlab.eclipse.org/eclipse/titan/titan.EclipsePlug-ins/-/issues/137jump to definition is sometimes jumping to the enclosing function2021-05-06T10:38:10ZEclipse Webmasterjump to definition is sometimes jumping to the enclosing function## Submitted by Kristof Szabados
Assigned to **Jeno Attila Balasko**
**[Link to original bug (#497133)](https://bugs.eclipse.org/bugs/xmlrpc.cgishow_bug.cgi?id=497133)**
## Description
Jump to definition is not working correctly i...## Submitted by Kristof Szabados
Assigned to **Jeno Attila Balasko**
**[Link to original bug (#497133)](https://bugs.eclipse.org/bugs/xmlrpc.cgishow_bug.cgi?id=497133)**
## Description
Jump to definition is not working correctly in some cases.
When the module is excluded, the cursor is not over a definition, or for some reason the module can not be identified.
In these cases the F3 functionality will jump to the beginning of the function it is invoked in.
This is not the right location to jump to, and also moves the cursor away from the place it was invoked from (users need to find their way back)
for example:
"
function f_functionName( )
{
var template integer valtozo := 5;
if(valueof(valtozo) == valueof(valtozo)) {
}
}
"
If the cursor is at "value_of" the F3 will jump to the name of the function.
Version: 5.5.0