catch signals for clean termination
Open
Nobody has claimed this yet.
question
- Dominant language
- C
- Stars
- 122
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
If a job gets terminated by the system (wall time, etc.) we currently leave stale state behind. We should catch SIGTERM and friends and cleanly terminate the server/client.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the server and client termination paths and any existing signal-handling entry points. Trace how SIGTERM and related system termination signals currently affect cleanup, then verify that termination removes stale state and cleanly stops both components.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100