anomalyco / anomalyco/opencode-drive
Add explicit abrupt server termination for restart probes
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 32
- Forks
- 3
- Avg merge
- 12m
- Merged PRs (30d)
- 17
Description
Drive 2.0.1, OpenCode c76e602ba4. server.kill() sends SIGTERM before escalating to SIGKILL, so a restart probe can accidentally verify only graceful cancellation. A compaction crash regression reproduces only when shutdown finalizers do not run.
An explicit crash or kill-signal option would make this deterministic and retain Drive’s expected-disconnect handling. Current workaround in the isolated fixture is to read opencode.health.get(), SIGSTOP that private server PID, then call server.kill() and server.launch(). This forces escalation without treating the exit as an unexpected run failure.
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 isolated fixture and the server.kill()/server.launch() lifecycle, including the opencode.health.get() workaround described in the issue. Add an explicit abrupt-termination option that preserves expected-disconnect handling, then use it in the restart probe and verify the compaction crash regression without relying on SIGSTOP or graceful-shutdown escalation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100