Support route-specific HTTP failures in network fixtures
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 58/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- bun, typescript
- Domain
- networking, testing-qa
Research direction
Start by locating the network fixture and its isolated controls, then compare them with the loopback proxy workaround described in the issue. Done means a selected method/path can return a deterministic status and body, matching request counts can be inspected, the override can be removed, and the route can heal for a Retry without restarting the instance.
Written by the indexing model from the issue text.
Description
Drive 2.0.1 can apply connection-level chaos, but reproducing an OpenCode TUI location-sync regression required a small loopback proxy to return HTTP 500 for only GET /api/agent while GET /api/location and SSE remain healthy. The same setup needs to heal that route and click Retry without restarting the instance.
A scoped HTTP fault override in the network fixture would make this repeatable without a Bun preload/proxy. Expected: select a method/path, return a deterministic status/body, inspect matching request counts, and remove the override. Current workaround: preload a loopback proxy for the script-owned TUI only, forward other requests, and toggle the selected response from the isolated fixture. OpenCode base tested: d9c85d8d95. This is a Drive fixture capability request, not the OpenCode bug itself.
- 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
-
refactor
Difficulty 2/5 Half a day Newbie friendliness 84/100
Maintainers usually reply within 5 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
OHDSI/Data2Evidence#3450 ·
Maintainers usually reply within 2 days
-
e2e-failure ready-to-code
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
redhat-developer/rhdh-plugin-export-overlays#4011 · 1 comment ·
Maintainers usually reply within 1 day
-
automation missing-model model-sync provider:ofox
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
anomalyco/models.dev#8421 ·
Maintainers usually reply within 1 day
-
SlackAdapter and TelegramAdapter are not assignable to Adapter under exactOptionalPropertyTypesOpen
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day