elonen / elonen/lanscatter

Make GUI kill processes forcibly after a short timeout

Open
#8 1 comment 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Python
Stars
2
Forks
1
PR merge metrics
No merged PRs in 30d

Description

Currently GUI can linger for quite a while in some cases, and keep sockets bound etc.

"Close" event should probably wait for nice shutdown for a few seconds, and then just kill everything if necessary.

Master doesn't write to disk at all, and client just rehashes stuff on startup, so corrupting files or such shouldn't be a problem.

Contributor guide

No contributing guide indexed for this repository

Research direction

Locate the GUI "Close" event and trace how the master and client processes shut down, including where sockets remain bound. Confirm the existing graceful-shutdown path, then verify that closing waits briefly before forcibly terminating any processes that remain; done means the GUI exits promptly without lingering processes or bound sockets.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
desktop, networking
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.