Repository navigation
docs: correct H9 access and context evidence, record CI enforcement - #47
Conversation
Walter runs no SSH, RDP or WinRM service (TCP probes 2026-10-01), so the SSH timeouts are expected, not a failed probe. Record the 2026-09-25 benchmark out-of-memory for qwen3-coder:30b on Walter at the default 131,072-token context and its 8,192-token success, as a likely contributor to the September 23 failure that remains unestablished. Add the runners' context-size difference and a pre-dispatch check. Record that main had no branch protection until 2026-10-01 and now requires the three CI checks for pull-request merges. No runner, threshold, version or ledger change.
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 55c4205dfa
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| Added 2026-10-01 after the reconciliation above. Each item carries its own date and source. | ||
|
|
||
| - **Walter runs no remote-shell service (Confirmed 2026-10-01).** Tailscale lists Walter as a Windows host. Five-second TCP probes to SSH (22), RDP (3389) and WinRM (5985, 5986) all timed out; only the Ollama API port answered. Tailscale SSH does not run on Windows hosts. The September 23 and October 1 SSH timeouts match this configuration and are not evidence of a fault. SSH cannot supply the diagnostic access the [results](DAVEHARNESS_H9_RESULTS.md) resume condition asks for; node-side diagnosis goes through the read-only Ollama API or through Dave at Walter (Ollama app settings and server log). |
There was a problem hiding this comment.
A TCP timeout proves only that the probe received no response; a firewall, ACL, alternate port, or interface binding produces the same result. Walter being Windows rules out Tailscale's integrated SSH server, but it does not rule out Windows OpenSSH, WinRM, or RDP. Therefore the “confirmed” absence of any remote-shell service—and the resulting claim that these timeouts are expected—is not established by the cited evidence and could cause future diagnostics to discard a valid access path. Record these ports as unreachable from the probing host unless the machine's service configuration was actually inspected.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Fixed in 19c5bd9: the review now says the ports are unreachable from the tailnet, notes that a firewall, binding or stopped service looks the same, and says Walter's service configuration was not inspected. The same applies to the results doc.
A TCP timeout shows only that the probe got no answer; a firewall, binding or stopped service looks the same, and Walter's service configuration was not inspected (Codex review on #47).
1 participant
Follow-up to #46. Docs only: no runner, threshold, version, ledger or authorization change.
Corrections
qwen3-coder:30bon Walter at the default 131,072-token context. Atnum_ctx8,192 it ran at 21.56 tok/s. The review now records this as a likely contributor to the Sept 23model_error. It is still not established: the 120 s timeout isn't explained by it, and the Sept 23 record has no node-side error text. The original "not established" finding is preserved./v1, so the node's setting decides. The adapter runner sendsnum_ctx≤ 16,384. Added as a table row, plus a pre-dispatch check.mainhad no branch protection or rulesets until 2026-10-01. It now requireschecks (3.12/3.13/3.14)from GitHub Actions for PR merges. Admins are not enforced, and branches need not be up to date. TheCLAUDE.mdwording changed from "enforces" to "runs", plus the protection note.Validation
pytest -q: 757 passed, 1 skipped (local; 1 platform skip).tests/test_documentation_contracts.py: 5 passed.git diff --check: clean.