Hi all,

after installing ACE 11.0.0.9, importing my flows, connecting to a remote integration node and starting up the debugger, the debug line in the toolkit loses synchronicity with the actual code.

This apparently happens when the debugger encounters a comment line. If one does a line by line debugging, the debugger stops at a comment line, as if it came across a line of code. 
After that, the position of the marker no longer matches the code.

The behavior occurs with every source code, always after the first comment after the first break point

Of course I made sure that the installed code matches the code in the toolkit, but it looks exactly like there is a difference.

Before I worked with version 11.0.0.8 without this occurring. The behavior only became apparent after the additional installation of the new version. In the "old" version, which still existed in parallel, it also appeared there afterwards.

I uninstalled all versions and deleted all the remains on the disk .. (I hope) .. but after the new installation of 11.0.0.9 the behavior remains.
It works completely normally on another computer with the same source and the same remote connection.. 

Oh.. it is a windows 10 machine.. (well both are..)

Example:


------------------------------
Michael Pecka
------------------------------

- Have you tried completely new workspace ?
- Does the debugger work properly for local (Int node running locally ) deployment?

------------------------------
Raj Sethi
------------------------------

Original Message:
Sent: Tue June 30, 2020 06:53 AM
From: Michael Pecka
Subject: Irritating behavior of the debugger in ACE 11.0.0.9

Hi all,

after installing ACE 11.0.0.9, importing my flows, connecting to a remote integration node and starting up the debugger, the debug line in the toolkit loses synchronicity with the actual code.

This apparently happens when the debugger encounters a comment line. If one does a line by line debugging, the debugger stops at a comment line, as if it came across a line of code. 
After that, the position of the marker no longer matches the code.

The behavior occurs with every source code, always after the first comment after the first break point

Of course I made sure that the installed code matches the code in the toolkit, but it looks exactly like there is a difference.

Before I worked with version 11.0.0.8 without this occurring. The behavior only became apparent after the additional installation of the new version. In the "old" version, which still existed in parallel, it also appeared there afterwards.

I uninstalled all versions and deleted all the remains on the disk .. (I hope) .. but after the new installation of 11.0.0.9 the behavior remains.
It works completely normally on another computer with the same source and the same remote connection.. 

Oh.. it is a windows 10 machine.. (well both are..)

Example:

------------------------------
Michael Pecka
------------------------------

Hi Raj,

thans for your answer. Yes I have tried a "fresh" workspace as well. And yes, it does the same on a locale deployment.

------------------------------
Michael Pecka
------------------------------

Original Message:
Sent: Wed July 01, 2020 08:14 AM
From: Raj Sethi
Subject: Irritating behavior of the debugger in ACE 11.0.0.9

- Have you tried completely new workspace ?
- Does the debugger work properly for local (Int node running locally ) deployment?

------------------------------
Raj Sethi

Original Message:
Sent: Tue June 30, 2020 06:53 AM
From: Michael Pecka
Subject: Irritating behavior of the debugger in ACE 11.0.0.9

Hi all,

after installing ACE 11.0.0.9, importing my flows, connecting to a remote integration node and starting up the debugger, the debug line in the toolkit loses synchronicity with the actual code.

This apparently happens when the debugger encounters a comment line. If one does a line by line debugging, the debugger stops at a comment line, as if it came across a line of code. 
After that, the position of the marker no longer matches the code.

The behavior occurs with every source code, always after the first comment after the first break point

Of course I made sure that the installed code matches the code in the toolkit, but it looks exactly like there is a difference.

Before I worked with version 11.0.0.8 without this occurring. The behavior only became apparent after the additional installation of the new version. In the "old" version, which still existed in parallel, it also appeared there afterwards.

I uninstalled all versions and deleted all the remains on the disk .. (I hope) .. but after the new installation of 11.0.0.9 the behavior remains.
It works completely normally on another computer with the same source and the same remote connection.. 

Oh.. it is a windows 10 machine.. (well both are..)

Example:

------------------------------
Michael Pecka
------------------------------