thefrontside / thefrontside/effectionx
Investigate daemon exit supervision on Windows
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 12
- Forks
- 4
- Avg merge
- 3h 17m
- Merged PRs (30d)
- 1
Description
The premature daemon-exit regression coverage added in #238 is currently skipped on Windows.
The test starts two daemons, terminates one with SIGTERM, expects the owning scope to raise DaemonExitError, and verifies that structured concurrency terminates the sibling process. This behavior needs investigation on Windows, where process signaling and tree termination differ from POSIX.
Acceptance criteria
- Determine why the signal-based daemon supervision test is unreliable or unsupported on Windows.
- Confirm that premature daemon exits propagate
DaemonExitErrorthrough the defaultProcessApipath. - Confirm that sibling daemon processes are terminated.
- Assert the appropriate Windows exit status semantics.
- Remove the Windows-only test skip from
process/test/daemon.test.ts.
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 with the skipped Windows coverage in process/test/daemon.test.ts and compare it with the premature daemon-exit regression added in #238. Investigate the default ProcessApi behavior for signal handling, sibling termination, and Windows exit statuses; done means the test runs without the Windows-only skip and verifies all listed acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- operating-systems, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100