Common Errors/en - Versionsgeschichte

Cg: /* Failed to load Shared Library */

2025-06-11T22:45:09Z

Failed to load Shared Library

← Nächstältere Version		Version vom 11. Juni 2025, 22:45 Uhr
Zeile 211:		Zeile 211:

	Ensure that the shared libraries are found. Under Unix/Linux, you may want to set the LD_LIBRARY_PATH shell variable; under Windows, dlls are searched along the PATH and in the cBridge.exe's own folder.		Ensure that the shared libraries are found. Under Unix/Linux, you may want to set the LD_LIBRARY_PATH shell variable; under Windows, dlls are searched along the PATH and in the cBridge.exe's own folder.
	A best practice is to set it before expecco is started, usually in your loginrc file. As alternative, set it in "''Extras''"- "''Settings''" - "''Execution''" - "''External Script Interpreters''". The standard library also contains an action to set the PATH inside the bridge.		A best practice is to set it before expecco is started, usually in your loginrc file. As alternative, set it in "''Extras''" → "''Settings''" → "''Execution''" → "''External Script Interpreters''". The standard library also contains an action to set the PATH inside the bridge.

	You can also take one of the existing compile scripts in the bridge folder, copy it to a new name, and add your shared library to the link command at the end. Then specify this compile script in your expecco settings.		You can also take one of the existing compile scripts in the bridge folder, copy it to a new name, and add your shared library to the link command at the end. Then specify this compile script in your expecco settings.

Cg: /* Running out of File Descriptors */

2025-06-11T22:44:05Z

Running out of File Descriptors

← Nächstältere Version		Version vom 11. Juni 2025, 22:44 Uhr
Zeile 31:		Zeile 31:
	You may then - after opening thousands of such files - run out of file descriptors, which will lead to an error during execution and also when you want to save the suite (or perform any other file operation).		You may then - after opening thousands of such files - run out of file descriptors, which will lead to an error during execution and also when you want to save the suite (or perform any other file operation).

	You can check for this situation by opening the external stream monitor via "''Extras''" - "''Debugging''" - "''External Stream Monitor''". If the list looks suspicious (i.e. super large), or contains files you think need to be closed, select them (use shift- or control click to select multiple) and choose the menu's "''Close''"function.		You can check for this situation by opening the external stream monitor via "''Extras''" → "''Debugging''" → "''External Stream Monitor''". If the list looks suspicious (i.e. super large), or contains files you think need to be closed, select them (use shift- or control click to select multiple) and choose the menu's "''Close''"function.

	Fix your test case(s) to make sure, files are closed.		Fix your test case(s) to make sure, files are closed.

Cg: /* ENOENT spawn git (when installing npm packages) */

2024-01-25T21:17:35Z

ENOENT spawn git (when installing npm packages)

← Nächstältere Version		Version vom 25. Januar 2024, 21:17 Uhr
Zeile 303:		Zeile 303:

	== Other Errors ==		== Other Errors ==
	===== ENOENT spawn git (when installing npm packages) =====		===== Python: ENOENT spawn git (when installing npm packages) =====

	"npm" might need git for its operation.		"npm" might need git for its operation.

Cg: /* TypeError: Object of type X is not JSON serializable */

2024-01-25T21:15:48Z

TypeError: Object of type X is not JSON serializable

← Nächstältere Version		Version vom 25. Januar 2024, 21:15 Uhr
Zeile 248:		Zeile 248:
	* define the pin's type as String, and write "str(obj)" to it. Thus effectively passing a printed string representation. However, you might have to define an extra decoding action in expecco for the object to be decoded (typically into an instance of a user defined compound type).		* define the pin's type as String, and write "str(obj)" to it. Thus effectively passing a printed string representation. However, you might have to define an extra decoding action in expecco for the object to be decoded (typically into an instance of a user defined compound type).

	* send a reference to the object to the output pin (i.e. write "makeRef(obj)" to it). This will transfer a transparent handle (think of it as a pointer) to the object to expecco. You may then later send the object reference back to Python, but it ~~will~~ may be harder to extract fields inside expecco (best is to define getter-actions to the fields in python and invoke those later).		* send a reference to the object to the output pin (i.e. write "makeRef(obj)" to it). This will transfer a transparent handle (think of it as a pointer) to the object to expecco. You may then later send the object reference back to Python, but it may be harder to extract fields inside expecco (best is to define getter-actions to the fields in python and invoke those later).

	* extract the required fields and send them to individual output pins (instead of writing the object as a whole)		* extract the required fields and send them to individual output pins (instead of writing the object as a whole)

Cg: /* Package not Found (although it was previously installed) */

2024-01-25T21:14:50Z

Package not Found (although it was previously installed)

← Nächstältere Version		Version vom 25. Januar 2024, 21:14 Uhr
Zeile 234:		Zeile 234:

	===== Package not Found (although it was previously installed) =====		===== Package not Found (although it was previously installed) =====
	Individual Python versions use different folders where they install and later search their packages. If a package is installed in a (say) Python3.7 installation, it will not be found by a previously installed Python2.7 or Python3.9 version.		Individual Python versions use different folders where they install and later search their packages. If a package is installed in a (say) Python3.7 installation, it will not be found by a previously installed Python2.7 or another Python3.9 version.

	The situation becomes even more confusing when "pip install" is used: you have to double check, where pip is going to install the package.		The situation becomes even more confusing when "pip install" is used: you have to double check, where pip is going to install the package.

Cg: /* Running out of File Descriptors */

2024-01-25T21:12:53Z

Running out of File Descriptors

← Nächstältere Version		Version vom 25. Januar 2024, 21:12 Uhr
Zeile 31:		Zeile 31:
	You may then - after opening thousands of such files - run out of file descriptors, which will lead to an error during execution and also when you want to save the suite (or perform any other file operation).		You may then - after opening thousands of such files - run out of file descriptors, which will lead to an error during execution and also when you want to save the suite (or perform any other file operation).

	You can check for this situation by opening the external stream monitor via "''Extras''" - "''Debugging''" - "'External Stream Monitor''". If the list looks suspicious (i.e. super large), or contains files you think need to be closed, select them (use shift- or control click to select multiple) and choose the menu's "''Close''"function.		You can check for this situation by opening the external stream monitor via "''Extras''" - "''Debugging''" - "''External Stream Monitor''". If the list looks suspicious (i.e. super large), or contains files you think need to be closed, select them (use shift- or control click to select multiple) and choose the menu's "''Close''"function.

	Fix your test case(s) to make sure, files are closed.		Fix your test case(s) to make sure, files are closed.

Cg: /* Failed to load Shared Library */

2024-01-25T21:11:21Z

Failed to load Shared Library

← Nächstältere Version		Version vom 25. Januar 2024, 21:11 Uhr
Zeile 207:		Zeile 207:

	Ensure that a correct toolchain (as called by the configured compile-script) is invoked. A common error on windows is a mismatch between a 64/32 bit cBridge and a 32/64 bit toolchain. The cBridge will report an error 193 when trying to load a generated or dependent dll.		Ensure that a correct toolchain (as called by the configured compile-script) is invoked. A common error on windows is a mismatch between a 64/32 bit cBridge and a 32/64 bit toolchain. The cBridge will report an error 193 when trying to load a generated or dependent dll.

			On Windows, virus scanners sometimes prevent a file from being loaded. The cBridge will report an error 126 when trying to load a generated or dependent dll which is currently locked by the scanner. Starting with expecco 23.2.77, the cBridge will retry the dll-load a few times as a workaround.

	Ensure that the shared libraries are found. Under Unix/Linux, you may want to set the LD_LIBRARY_PATH shell variable; under Windows, dlls are searched along the PATH and in the cBridge.exe's own folder.		Ensure that the shared libraries are found. Under Unix/Linux, you may want to set the LD_LIBRARY_PATH shell variable; under Windows, dlls are searched along the PATH and in the cBridge.exe's own folder.

Cg: /* Failed to load Shared Library */

2024-01-25T21:08:37Z

Failed to load Shared Library

← Nächstältere Version		Version vom 25. Januar 2024, 21:08 Uhr
Zeile 206:		Zeile 206:
	This issue refers to bridged C actions - not DLL actions.		This issue refers to bridged C actions - not DLL actions.

			Ensure that a correct toolchain (as called by the configured compile-script) is invoked. A common error on windows is a mismatch between a 64/32 bit cBridge and a 32/64 bit toolchain. The cBridge will report an error 193 when trying to load a generated or dependent dll.
⚫	~~Ensure that the shared libraries are found. Under Unix/Linux, you may want to set the LD_LIBRARY_PATH shell variable.~~ A best practice is to set it before expecco is started, usually in your loginrc file. As alternative, set it in "''Extras''"- "''Settings''" - "''Execution''" - "''External Script Interpreters''".

			Ensure that the shared libraries are found. Under Unix/Linux, you may want to set the LD_LIBRARY_PATH shell variable; under Windows, dlls are searched along the PATH and in the cBridge.exe's own folder.
		⚫	A best practice is to set it before expecco is started, usually in your loginrc file. As alternative, set it in "''Extras''"- "''Settings''" - "''Execution''" - "''External Script Interpreters''". The standard library also contains an action to set the PATH inside the bridge.

	You can also take one of the existing compile scripts in the bridge folder, copy it to a new name, and add your shared library to the link command at the end. Then specify this compile script in your expecco settings.		You can also take one of the existing compile scripts in the bridge folder, copy it to a new name, and add your shared library to the link command at the end. Then specify this compile script in your expecco settings.
	Consult the compiler-toolchain's manual pages on how shared libraries are searched and resolved;		Consult the compiler-toolchain's manual pages on how shared libraries are searched and resolved;
	typically there is a ~~command line~~ argument for the linker (such as -L or -linkPath) which tells the executable where libraries are to be found.		typically there is a commandline argument for the linker (such as -L or -linkPath) which tells the executable where libraries are to be found.

	If all fails, copy or symlink your shared library to the cBridge folder ("<code>installDir/packages/exept/expecco/bridgeFramework/cBridge</code>").		If all fails, copy or symlink your shared library to the cBridge folder ("<code>installDir/packages/exept/expecco/bridgeFramework/cBridge</code>").

Cg: /* Wrong Input Valus in a Chain of Looped-Over Steps */

2022-03-17T12:46:10Z

Wrong Input Valus in a Chain of Looped-Over Steps

← Nächstältere Version		Version vom 17. März 2022, 12:46 Uhr
Zeile 277:		Zeile 277:


	===== Wrong Input ~~Valus~~ in a Chain of Looped-Over Steps =====		===== Wrong Input Values in a Chain of Looped-Over Steps =====

	Imagine a number of steps in a chain,		Imagine a number of steps in a chain,

Cg: /* Step in Loop is not Executed at All */

2022-03-17T12:23:29Z

Step in Loop is not Executed at All

← Nächstältere Version		Version vom 17. März 2022, 12:23 Uhr
Zeile 269:		Zeile 269:

	Fix:		Fix:
	* To provide this initial trigger, add any dummy step, which generates an output and feed that as additional input to the loop-top's enableIn pin~~. Any output and especially a trigger-output will do~~.		* To provide this initial trigger, add any dummy step, which generates an output and feed that as additional input to the loop-top's enableIn pin.
			:Any output and especially a trigger-output will do.
	:		:
	:		:
	:The standard library provides such a block named "Start", which is actually a No-Operation block, and its sole purpose is to provide such an initial trigger condition~~. Make sure that the Start step is itself triggered, usually by setting its autostart execution flag~~.		:The standard library provides such a block named "Start", which is actually a No-Operation block, and its sole purpose is to provide such an initial trigger condition.
			:Make sure that the Start step is itself triggered, usually by setting its autostart execution flag.