Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Command timeouts #196

Open
WebFreak001 opened this issue Aug 26, 2016 · 0 comments
Open

Command timeouts #196

WebFreak001 opened this issue Aug 26, 2016 · 0 comments

Comments

@WebFreak001
Copy link
Member

WebFreak001 commented Aug 26, 2016

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

@WebFreak001 WebFreak001 transferred this issue from Pure-D/workspace-d Feb 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant