Open lzzzam opened 11 months ago
UPDATE: it seems that adding a little delay into each task seems to fix problem, something like
time.sleep(0.2)
hi, thanks for reporting this, I'll check what's going on.
After some investigations on different OS and browsers I wasn't able to reproduce this issue, though it seems bound to the websocket and not to the pipeline executor, I'll try to handle those websocket connection issues!
Tried a basic pipeline to check how return values are used in the GUI. The first run of the following simple code seems to generate unstable behaviour:
Here the output log: