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

Option to kill RAFCON if execution cannot be stopped #522

Open
2 tasks
franzlst opened this issue Apr 17, 2020 · 1 comment
Open
2 tasks

Option to kill RAFCON if execution cannot be stopped #522

franzlst opened this issue Apr 17, 2020 · 1 comment

Comments

@franzlst
Copy link
Member

After stopping the execution, it might happen that a thread does not join. If RAFCON is closed, the prevents the process from being stopped.

If the execution is still active after a certain amount of time, the user should have the option that the process is killed (os.exit()).

added by @Rbelder:

  • so a dialog should be open if the engine is not stopping within a certain duration which offers
    • to let the thread and process life (but with a note how to kill it in the console later)
    • or to directly kill it by os.exit()
  • additional sub-task would be to check if the same interface is possible for core only and to implement it in e.g. the interface-module which is in core and gui sub-package

Originally created by @franzlst ([email protected]) at 2018-05-02 11:29:15+00:00 (moved from RMC internal repository)

@franzlst
Copy link
Member Author

See also: #512

Originally created by @franzlst ([email protected]) at 2018-05-02 11:29:29+00:00 (moved from RMC internal repository)

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