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

[Feature request (NT)] - Implement a Proper Stop Mechanism for Interamap #352

Open
zangjiucheng opened this issue Feb 2, 2025 · 0 comments
Labels
enhancement New feature or request

Comments

@zangjiucheng
Copy link
Member

Feature Description

Describe the feature

Currently, there is no proper way to stop Interamap once it has started. Since it spawns multiple sub-processes (e.g., live-point server, HTTP server, etc.), stopping the UI does not terminate the background processes, which continue running. This can lead to resource consumption issues and potential conflicts when restarting the application.

Image

Expected behavior

  • Provide a way to gracefully terminate all running servers and sub-processes with a single action.
  • Allow users to stop all processes using a single Ctrl + C command in the terminal.
  • Ensure that all sub-processes started by Interamap are properly cleaned up on exit.
  • Implement this stop mechanism within the launcher as well, ensuring that all associated services are terminated when the launcher stops Interamap.

Additional context

  • Properly test the implementation to ensure that all spawned processes are correctly terminated when Interamap is stopped.
  • Consider adding logging to confirm that each sub-process shuts down as expected.
@zangjiucheng zangjiucheng added the enhancement New feature or request label Feb 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant