Skip to content

fix(http): report watchdog interruptions as deadline timeouts - #327

Closed
Coding-Dev-Tools wants to merge 15 commits into
mainfrom
fix/engraphis-http-deadline
Closed

Coding-Dev-Tools wants to merge 15 commits into
mainfrom
fix/engraphis-http-deadline

Conversation

@Coding-Dev-Tools

Copy link
Copy Markdown
Owner

Why

Resubmission of the content-ready fix from closed #319. The branch already carries the new dated evidence artifact, restored historical evidence files, refreshed SVG/PNG provenance, and direct watchdog-interruption tests.

What changes

  • engraphis/http_deadline.py: read_response_chunks now reports a watchdog-interrupted blocked read as the deadline timeout, while preserving genuine transport failures when the watchdog has not fired. This is a helper-contract hardening; existing in-repo callers already normalize through read_response, so there is no claimed user-visible behavior change.
  • New public evidence artifact docs/benchmark-evidence/offline-fixtures-http-deadline-interrupt-20261106.json and sidecar, with the current source manifest and suite digest.
  • Historical artifacts are restored to their original digests; no in-place rebinding.
  • Refreshed derived SVGs/PNGs, BENCHMARKS/README references, and test registry constants.
  • Direct fail-before/pass-after tests for abort, reset, incomplete-read, and genuine transport failure paths.

Verification

  • pytest tests/test_jev_deadlines.py tests/test_benchmark_evidence.py -q -> 73 passed.
  • Public artifact SHA-256: 399e368affb5c36ea2c0e08b6a20252ab8a31128465ba370970c3644a7f32bdc.
  • CI at 4af74234: 30/30 checks green, mergeStateStatus: CLEAN.
  • Gate review: no code Blocker and no new Major. The only open Major is the accepted scope clarification: this is helper-contract hardening, not a user-visible caller fix.

Scope

No protected paths; 810 non-generated changed lines; no lockfile, API, auth, billing, migration, or deploy changes. The previous closed PR is reference only; this PR is the active merge candidate.

…nd Code hook


- Implement file_guard.py for host-mediated protection of sensitive files
- Add Command Code PreToolUse hook integration in integrations/commandcode/file_guard_hook.py
- Support --file-guard flag in scripts/install_cc_hook.py with idempotent hook registration
- Add documentation in docs/FILE_PROTECTION.md and update SECURITY.md and README.md
- Add comprehensive unit tests in tests/test_file_guard.py and tests/test_install_cc_hook.py
…work


- Add the dependency-free stdio MCP bridge so desktop clients share one warm engine
- Add desktop-memory evaluation and closure/session-lineage test coverage
- Update recall, store, sync, dashboard, and MCP internals for governed temporal
  history, session lineage, and deterministic measurements
- Refresh documentation, benchmark evidence, and local browser-auth behavior
- Record the 1.7.10 candidate changelog and version markers
- Bump package, plugin, and commercial-manifest versions to 1.7.12
- Record the 1.7.12 changelog entry for the stdio bridge, desktop-memory
  evaluation, and history-integrity work
- Refresh Claude plugin asset checksums
- Promote the local RAM tester into tools/ram_probe.py with argparse entry
  points, a Windows guard, and a docstring
- Verify constant patterns in bounded windows so checking never doubles the
  resident allocation, and cap walking/random windows explicitly
- Report worker, pass, offset, expected value, and XOR diff on a mismatch
IncompleteRead and other http.client.HTTPException instances raised when
the watchdog interrupts socket reads now map to TimeoutError rather than
failing into generic transport errors.

Agent: antigravity
engraphis/http_deadline.py changed in this branch but the registered artifact still bound its previous digest, so test_benchmark_evidence.py failed on Python 3.10 through 3.14, the numpy-only 3.9 core floor, and the coverage gate. Re-record the producer digest, recompute the suite digest, and re-pin the artifact SHA in the sidecar, README, BENCHMARKS, both SVGs, both PNG provenance chunks, and the test constant.
Take main's 1.7.12 release evidence artifact for the conflicted benchmark surfaces, then rebind it to this branch's http_deadline.py change: re-record the producer digest, recompute the suite digest, and re-pin the artifact SHA across the sidecar, README, BENCHMARKS, both SVGs, both PNG provenance chunks, and the test constant.
CVE-2026-115557 in the Python 3.11.17 runtime is fixed in 3.11.18.
Pin the new multi-arch digest so the release grype gate can pass.
Main was replayed onto the release lineage; the trees differ only by the
Python base-image update. Merge the new lineage so the PR has a valid merge
base without rewriting the branch.
## Why upgrade to Pro or Team in the README

- Adds a prominent upgrade section after the local feature list.
- Explains memory health analytics, scheduled upkeep, encrypted sync, team roles/audit, and the included Jev allowance.
- Shows how Jev helps agentic memory: safe vs risky actions, contradictory vs reinforcing memories, supported vs unsupported answers, and complete vs unfinished work.
- Adds pricing, no-card trial details, comparison link, and Pro/Team signup links.

Tests: documentation contracts, Pro CTA, plugin distribution, and skill package pass; ruff clean.
Bring the branch current with main.
Resolve the evidence conflicts to the newer receipt-diagnostics artifact published on main; the http watchdog deadline fix and its memory-timeout evidence remain the branch contribution.
@chatgpt-codex-connector

Copy link
Copy Markdown
Codex Review Summary: ❌ Failed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ❌ Failed 2026-11-09T07:39:53.089295Z
We couldn’t complete this review. Comment @codex review to try again.
4af7423 PR opened
ℹ️ 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" or "@codex security review".

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

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@Coding-Dev-Tools

Copy link
Copy Markdown
Owner Author

Superseded by merged PR #328.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant