Add explicit abrupt server termination for restart probes
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 62/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- testing
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.
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.
- Dominant language
- TypeScript
- Stars
- 32
- Forks
- 4
- Avg merge
- 10m
- Merged PRs (30d)
- 13
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from anomalyco/opencode-drive
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
anomalyco/opencode-drive#102 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 58/100
anomalyco/opencode-drive#104 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 50/100
anomalyco/opencode-drive#103 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 55/100
anomalyco/opencode-drive#97 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 3/5 1-2 days Newbie friendliness 68/100
anomalyco/opencode-drive#86 · 1 comment ·
Maintainers usually reply within 1 day
All issues in anomalyco/opencode-drive
Similar issues
-
priority: P2
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
prime-radiant-inc/evener#3291 ·
Maintainers usually reply within 1 day
-
accessibility bug revealjs
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
quarto-dev/quarto-cli#14961 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
supabase/agent-skills#614 ·
-
Content
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
RunestoneInteractive/rs#1559 · 1 comment ·
Maintainers usually reply within 2 days