Occasional timeout Error in log since javascript 7.2.0

[GitHoubi]

Describe the bug
Since version 7.2. of the javascript Adapater I have timeout errors in two of my Blocky scripts. As far as I can see, everything regarding the scripts themselves works perfectly. The only thing is that these timeout errors keep appearing in the log.

This behavior is identical for versions 7.2.0, 7.3.0 and 7.4.0. If I go back to 7.1.6, the timeout errors also disappear, this can be reproduced as often as required.

To Reproduce
Force SendTo action

Expected behavior
No Timeout Errors in the Log as with 7.1.6 or older

Screenshots & Logfiles

Versions:

• Adapter version: 7.2.0, 7.3.0, 7.4.0
• JS-Controller version: 5.0.17
• Node version: v18.19.0
• Operating system: Debian Bookworm

[klein0r]

Already fixed in b9f5860

Thanks for testing this beta version

[GitHoubi]

Already fixed in b9f5860

Thanks for testing this beta version

Hi Matthias

Klappt wunderbar mit dem neuen sandbox.js file, hab vielen herzlichen Dank.

[GitHoubi]

fixed with b9f5860

[passuff]

I'm still facing this error with javascript 8.03.
It seems to be connected to "send to" function block.

[klein0r]

It seems to be connected to "send to" function block.

Yes, it can happen if you provide a callback function but you use sendTo to "all instances". In that case no instance returns a result and the sandbox returns a timeout (to ensure the async methods will not block forever).

@passuff Please share some code / examples which generates that issue.

[Apollon77]

When I remember correctly in this case the first answer should be used as result and being returned .... at least on js.controller level

[zaphod2]

Abgesehen davon versteh ich den Timeout eh nicht, kann ich einstellen was ich will und gefühlt macht er was er will.

[klein0r]

@zaphod2 Welche version ist das? Bitte mit der aktuellsten beta testen.

[zaphod2]

Sorry, war v8.0.3
Habe jetzt mal v8.1.1 installiert.

[zaphod2]

Ist auch mit 8.1.1 vorhanden.

[zaphod2]

Ist auch mit 8.2.0 vorhanden.

[klein0r]

@zaphod2 Und wir auch in der nächsten Version enthalten sein, wenn sich hier am Issue nichts ändert...