You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit f56c09c
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: .agents/skills/build-from-issue/SKILL.md
+12-16Lines changed: 12 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -402,29 +402,24 @@ git diff --name-only main -- e2e/
402
402
403
403
If there are no changes under `e2e/`, skip this phase entirely.
404
404
405
-
If E2E files were modified, deploy to the local cluster and run the E2E test suite:
405
+
If E2E files were modified, run the relevant E2E lane for the driver touched by the change:
406
406
407
407
```bash
408
-
# Deploy all changes to the local k3s cluster
409
-
mise run cluster:deploy
410
-
411
-
# Run the E2E sandbox tests
412
-
mise run test:e2e:sandbox
408
+
# Docker-backed gateway smoke E2E
409
+
mise run e2e:docker
413
410
```
414
411
415
-
`mise run test:e2e:sandbox` depends on `cluster:deploy` and `python:proto`, then runs `uv run pytest -o python_files='test_*.py' e2e/python`. However, since the cluster may need explicit deploy for code changes beyond just E2E test files, always run `mise run cluster:deploy` first as a separate step to ensure all sandbox/proxy/policy changes are live on the cluster before running E2E tests.
412
+
Use `mise run e2e:podman`, `mise run e2e:vm`, or a Helm-backed Kubernetes E2E lane when the change targets those drivers.
416
413
417
414
**E2E retry loop** (up to 3 attempts):
418
415
419
-
1. Run `mise run cluster:deploy` (only on the first attempt, or if code was changed between attempts).
420
-
2. Run `mise run test:e2e:sandbox`.
421
-
3. If tests fail:
416
+
1. Run the selected E2E lane.
417
+
2. If tests fail:
422
418
- Read the pytest output carefully — identify which tests failed and why.
423
419
- Distinguish between **test bugs** (the test itself is wrong) and **implementation bugs** (the code under test is wrong).
424
420
- Fix the failing code or tests.
425
-
- If code changes were made (not just test fixes), re-run `mise run cluster:deploy` before retrying.
426
421
- Decrement the retry counter and try again.
427
-
4. If tests pass, Phase 2 is green.
422
+
3. If tests pass, Phase 2 is green.
428
423
429
424
**If all 3 E2E attempts fail**, stop and report to the user:
430
425
- Which E2E tests are failing
@@ -576,8 +571,8 @@ Local E2E tests passed. CI does not currently run E2E tests, so this comment ser
576
571
| Field | Value |
577
572
|-------|-------|
578
573
| **Commit** | `<commit-sha>` |
579
-
| **Command** | `mise run test:e2e:sandbox` |
580
-
| **Cluster deploy** | `mise run cluster:deploy` (completed before test run) |
-**`cluster inference is not configured`**: set the managed route with `openshell inference set`
177
+
-**`cluster inference is not configured`**: set the managed gateway route with `openshell inference set`
178
178
-**`connection not allowed by policy`** on `inference.local`: unsupported method or path
179
179
-**`no compatible route`**: provider type and client API shape do not match
180
180
-**Connection refused / upstream unavailable / verification failures**: base URL, bind address, topology, or credentials are wrong
@@ -232,7 +232,7 @@ In this case, OpenShell routing is usually working correctly. The failing hop is
232
232
233
233
This is not the same issue as the Colima CoreDNS fix.
234
234
235
-
OpenShell injects `host.docker.internal` and `host.openshell.internal` into sandbox pods with `hostAliases`. That path bypasses cluster DNS lookup. If the request still times out, the usual cause is host firewall or network policy, not CoreDNS.
235
+
OpenShell injects `host.docker.internal` and `host.openshell.internal` into sandbox workloads when the selected compute platform supports it. That path bypasses runtime DNS lookup. If the request still times out, the usual cause is host firewall or network policy, not DNS.
236
236
237
237
### Verify the Problem
238
238
@@ -248,40 +248,41 @@ OpenShell injects `host.docker.internal` and `host.openshell.internal` into sand
248
248
curl -sS http://172.17.0.1:11434/v1/models
249
249
```
250
250
251
-
3. Test the same endpoint from the OpenShell cluster container:
251
+
3. Test the same endpoint from a gateway or sandbox container on the Docker network:
If steps 1 and 2 succeed but step 3 times out, the host firewall or network configuration is blocking the container-to-host path.
258
259
259
260
### Fix
260
261
261
-
Allow the Docker bridge network used by the OpenShell cluster to reach the host-local inference port. The exact command depends on your firewall tooling (iptables, nftables, firewalld, UFW, etc.), but the rule should allow:
262
+
Allow the Docker bridge network used by the OpenShell gateway and sandbox containers to reach the host-local inference port. The exact command depends on your firewall tooling (iptables, nftables, firewalld, UFW, etc.), but the rule should allow:
262
263
263
-
-**Source**: the Docker bridge subnet used by the OpenShell cluster container (commonly `172.18.0.0/16`)
264
-
-**Destination**: the host gateway IP injected into sandbox pods for `host.docker.internal` (commonly `172.17.0.1`)
264
+
-**Source**: the Docker bridge subnet used by OpenShell containers (commonly `172.18.0.0/16`)
265
+
-**Destination**: the host gateway IP injected into sandbox workloads for `host.docker.internal` (commonly `172.17.0.1`)
265
266
-**Port**: the inference server port (e.g. `11434/tcp` for Ollama)
266
267
267
268
To find the actual values on your system:
268
269
269
270
```bash
270
-
# Docker bridge subnet for the OpenShell cluster network
0 commit comments