Test Editor/en - Versionsgeschichte

Cg: /* State Colors */

2026-02-26T20:18:01Z

State Colors

← Nächstältere Version		Version vom 26. Februar 2026, 20:18 Uhr
Zeile 145:		Zeile 145:
	* grey/original color<br>the step was not yet executed		* grey/original color<br>the step was not yet executed

	* blue (a light blue)<br>the step is about to be executed. This means that it has all of its input values (and possibly any required resources) available and it is ready to run. However, its code or network is not yet being executed - either because other steps are still running and the maximum execution ~~parallelity~~ has been reached, or because the diagram is being single stepped and waiting for you to press the "''Step Next''" button.		* blue (a light blue)<br>the step is about to be executed. This means that it has all of its input values (and possibly any required resources) available and it is ready to run. However, its code or network is not yet being executed - either because other steps are still running and the maximum execution parallelism has been reached, or because the diagram is being single stepped and waiting for you to press the "''Step Next''" button.

	* bright green (lime)<br>the step is being executed		* bright green (lime)<br>the step is being executed

Cg: /* Cannot start bridge... */

2025-04-30T00:11:52Z

Cannot start bridge...

← Nächstältere Version		Version vom 30. April 2025, 00:11 Uhr
Zeile 272:		Zeile 272:
	Solution:		Solution:
	* go to the settings dialog ("''Extras''" → "''Execution''" → "''External Script Interpreters''") and check the path setttings.		* go to the settings dialog ("''Extras''" → "''Execution''" → "''External Script Interpreters''") and check the path setttings.
	* to install, see [[~~Installing_additional_frameworks~~\|"Installing Additional Frameworks"]]		* to install, see [[Installing_additional_Frameworks/en\|"Installing Additional Frameworks"]]

	= See Also =		= See Also =

Cg: /* Cannot start bridge... */

2025-04-30T00:11:11Z

Cannot start bridge...

← Nächstältere Version		Version vom 30. April 2025, 00:11 Uhr
Zeile 265:		Zeile 265:
	=== Cannot start bridge... ===		=== Cannot start bridge... ===
	A script interpreter (ruby, python, node, etc.) was not found.		A script interpreter (ruby, python, node, etc.) was not found.

			This happens if:
			* the path to the interpreter command is incorrect
			* the language subsystem was not installed

	Solution:		Solution:
	* ~~got~~ to the settings dialog ("''Extras''" → "''Execution''" → "''External Script Interpreters''") and check the path setttings.		* go to the settings dialog ("''Extras''" → "''Execution''" → "''External Script Interpreters''") and check the path setttings.
			* to install, see [[Installing_additional_frameworks\|"Installing Additional Frameworks"]]

	= See Also =		= See Also =

Cg: /* No value for input pin "..." of step "..." */

2025-04-30T00:09:19Z

No value for input pin "..." of step "..."

← Nächstältere Version		Version vom 30. April 2025, 00:09 Uhr
Zeile 261:		Zeile 261:
	* make sure the inner pin is connected, and also that it will receive a value at the input pin(s). If it has an autostart or explicit trigger, check if that is really what you intended. In most cases, steps should be triggered by incoming data, and not only by control flow triggers (but to have both is perfectly ok).		* make sure the inner pin is connected, and also that it will receive a value at the input pin(s). If it has an autostart or explicit trigger, check if that is really what you intended. In most cases, steps should be triggered by incoming data, and not only by control flow triggers (but to have both is perfectly ok).
	:		:
	:Be especially careful when steps are in a loop: often an input value is "consumed"in the first iteration, and then no value is present in further loop cycles. Then, make the input a "non-consuming" (parameter) pin, to preserve the value across loop cycles. Usually happens if the step has multiple inputs of which one is fed from a generator and another from a single incoming value (and its that second pin, which should be made a parameter pin).		:'''Be especially careful when steps are in a loop''': often an input value is "consumed"in the first iteration, and then no value is present in further loop cycles. Then, make the input a "non-consuming" (parameter) pin, to preserve the value across loop cycles. Usually happens if the step has multiple inputs of which one is fed from a generator and another from a single incoming value (and its that second pin, which should be made a parameter pin).

	=== Cannot start bridge... ===		=== Cannot start bridge... ===

Cg: /* No value for input pin "..." of step "..." */

2025-04-30T00:08:56Z

No value for input pin "..." of step "..."

← Nächstältere Version		Version vom 30. April 2025, 00:08 Uhr
Zeile 253:		Zeile 253:
	=== No value for input pin "..." of step "..." ===		=== No value for input pin "..." of step "..." ===
	An inner step was started, but got no input value at one of its required pins.		An inner step was started, but got no input value at one of its required pins.

⚫	The inner step was started (probably due to autostart or an explicit trigger, bt not due to an input value arriving).
			This happens if:
		⚫	* The inner step was started (probably due to autostart or an explicit trigger, but not due to an input value arriving).
			* The step was started multiple times (for example in a loop or triggered by a generator), but some input value was consumed.

	Solution:		Solution:
	* make sure the inner pin is connected, and also that it will receive a value at the input pin(s). If it has an autostart or explicit trigger, check if that is really what you intended. In most cases, steps should be triggered by incoming data, and not only by control flow triggers (but to have both is perfectly ok).		* make sure the inner pin is connected, and also that it will receive a value at the input pin(s). If it has an autostart or explicit trigger, check if that is really what you intended. In most cases, steps should be triggered by incoming data, and not only by control flow triggers (but to have both is perfectly ok).
	:		:
	:Be especially careful when steps are in a loop: often an input value is "consumed"in the first iteration, and then no value is present in further loop cycles. Then, make the input a "non-consuming" (parameter) pin, to preserve the value across loop cycles.		:Be especially careful when steps are in a loop: often an input value is "consumed"in the first iteration, and then no value is present in further loop cycles. Then, make the input a "non-consuming" (parameter) pin, to preserve the value across loop cycles. Usually happens if the step has multiple inputs of which one is fed from a generator and another from a single incoming value (and its that second pin, which should be made a parameter pin).

	=== Cannot start bridge... ===		=== Cannot start bridge... ===

Cg: /* Cannot start bridge... */

2025-04-30T00:06:34Z

Cannot start bridge...

← Nächstältere Version		Version vom 30. April 2025, 00:06 Uhr
Zeile 262:		Zeile 262:
	=== Cannot start bridge... ===		=== Cannot start bridge... ===
	A script interpreter (ruby, python, node, etc.) was not found.		A script interpreter (ruby, python, node, etc.) was not found.

	Solution:		Solution:
	* got to the settings dialog ("''Extras''" → "''Execution''" → "''External Script Interpreters''") and check the path setttings.		* got to the settings dialog ("''Extras''" → "''Execution''" → "''External Script Interpreters''") and check the path setttings.

Cg: /* No value for input pin "..." of step "..." */

2025-04-30T00:06:13Z

No value for input pin "..." of step "..."

← Nächstältere Version		Version vom 30. April 2025, 00:06 Uhr
Zeile 259:		Zeile 259:
	:		:
	:Be especially careful when steps are in a loop: often an input value is "consumed"in the first iteration, and then no value is present in further loop cycles. Then, make the input a "non-consuming" (parameter) pin, to preserve the value across loop cycles.		:Be especially careful when steps are in a loop: often an input value is "consumed"in the first iteration, and then no value is present in further loop cycles. Then, make the input a "non-consuming" (parameter) pin, to preserve the value across loop cycles.

			=== Cannot start bridge... ===
			A script interpreter (ruby, python, node, etc.) was not found.
			Solution:
			* got to the settings dialog ("''Extras''" → "''Execution''" → "''External Script Interpreters''") and check the path setttings.

	= See Also =		= See Also =

Cg: /* No value for input pin "..." of step "..." */

2025-04-30T00:02:42Z

No value for input pin "..." of step "..."

← Nächstältere Version		Version vom 30. April 2025, 00:02 Uhr
Zeile 256:		Zeile 256:

	Solution:		Solution:
	:make sure the inner pin is connected, and also that it will receive a value at the input pin(s). If it has an autostart or explicit trigger, check if that is really what you intended. In most cases, steps should be triggered by incoming data, and not only by control flow triggers (but to have both is perfectly ok).		* make sure the inner pin is connected, and also that it will receive a value at the input pin(s). If it has an autostart or explicit trigger, check if that is really what you intended. In most cases, steps should be triggered by incoming data, and not only by control flow triggers (but to have both is perfectly ok).
	:		:
	:Be especially careful when steps are in a loop: often an input value is "consumed"in the first iteration, and then no value is present in further loop cycles. Then, make the input a "non-consuming" (parameter) pin, to preserve the value across loop cycles.		:Be especially careful when steps are in a loop: often an input value is "consumed"in the first iteration, and then no value is present in further loop cycles. Then, make the input a "non-consuming" (parameter) pin, to preserve the value across loop cycles.

Cg: /* No executable step in action "Test/Demo" */

2025-04-30T00:02:21Z

No executable step in action "Test/Demo"

← Nächstältere Version		Version vom 30. April 2025, 00:02 Uhr
Zeile 249:		Zeile 249:
	* and no inner step got a value at one of its required triggering pins (from the compound action).		* and no inner step got a value at one of its required triggering pins (from the compound action).
	Solution:		Solution:
	:provide an input value to the tested compound action in the "Test/Demo" diagram, or set the autostart attribute at a step.		* provide an input value to the tested compound action in the "Test/Demo" diagram, or set the autostart attribute at a step.

	=== No value for input pin "..." of step "..." ===		=== No value for input pin "..." of step "..." ===

Cg: /* No executable step in action "Test/Demo" */

2025-04-30T00:01:51Z

No executable step in action "Test/Demo"

← Nächstältere Version		Version vom 30. April 2025, 00:01 Uhr
Zeile 249:		Zeile 249:
	* and no inner step got a value at one of its required triggering pins (from the compound action).		* and no inner step got a value at one of its required triggering pins (from the compound action).
	Solution:		Solution:
	:~~typically, you forgot to~~ provide an input value to the tested compound action in the "Test/Demo" diagram, or ~~lost~~ the autostart attribute of a step.		:provide an input value to the tested compound action in the "Test/Demo" diagram, or set the autostart attribute at a step.

	=== No value for input pin "..." of step "..." ===		=== No value for input pin "..." of step "..." ===