You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes commands can start to hang for various reasons (invalid length, stuck in endless loop, child process hung up, etc)
There should be an attribute @timeout(Duration) which sets a timeout for the function. By default every function should have a timeout of 10 seconds.
When a function times out it wont be terminated, it will only send a timeout response (same as error) and if its synchronous it will be moved to another thread (for this they will start in the other thread already and the main thread will block until it times out or the response arrives).
If a timed out function actually returns afterwards it will send the response to message id 0x71 33 00 70 instead (timeout handler)
This will probably fix the occassional auto completion hang-ups on windows
The text was updated successfully, but these errors were encountered:
Sometimes commands can start to hang for various reasons (invalid length, stuck in endless loop, child process hung up, etc)
There should be an attribute
@timeout(Duration)
which sets a timeout for the function. By default every function should have a timeout of 10 seconds.When a function times out it wont be terminated, it will only send a timeout response (same as error) and if its synchronous it will be moved to another thread (for this they will start in the other thread already and the main thread will block until it times out or the response arrives).
If a timed out function actually returns afterwards it will send the response to message id
0x71 33 00 70
instead (timeout handler)This will probably fix the occassional auto completion hang-ups on windows
The text was updated successfully, but these errors were encountered: