Skip to content

[CC5-s1375d0] docs(txe): TXE-5670 the design doc says what an edge proof showed - #216

Merged
connorwang merged 1 commit into
mainfrom
cc5-s1375d0/txe-5670-design-edge-proof
Nov 2, 2026
Merged

connorwang merged 1 commit into
mainfrom
cc5-s1375d0/txe-5670-design-edge-proof

Conversation

@connorwang

Copy link
Copy Markdown
Collaborator

Summary

txe/worker/HTTPS-CHANNEL.md still said no Cloudflare path had been tried. A synthetic proof has since run through a Cloudflare Tunnel, with the real channel handler behind it. A new section, "Through an edge", says what that showed, in generic terms:

  • unary calls, and a refusal arriving as the channel's own;
  • 100 polls held beside 300 heartbeats;
  • 25 s and 35 s idle gaps inside a stream;
  • a 105 s stream;
  • a 16 MiB request, digest matching;
  • a connector restart read as a brief Unavailable;
  • a stopped origin read as Unavailable.

It also records two edge behaviours:

  • every request reached the edge over HTTP/2;
  • small request bodies were held until the request ended, while large ones streamed. The channel depends on neither.

What was not run is stated, with why: the at-limit and over-limit requests could not fit the stream limit at the link's rate, so they were skipped, not passed. The section points to the fixture's lowered cap (#215) that lets them fit.

The status line and the open questions are updated to match.

Kept out: hostnames, zone settings, access configuration, security posture and reachability. This is the fixture and the protocol, not the production uploader, a real hub, a real identity provider or a real worker, and the doc says so.

Tests

Docs only.

Closes TXE-5670

🤖 Generated with Claude Code

…oof showed

HTTPS-CHANNEL.md still said no Cloudflare path had been tried. It now says
what the synthetic proof through a Cloudflare Tunnel showed, in generic
terms: unary calls and refusals, held polls, idle gaps, a long stream, a
16 MiB request, a connector restart and a stopped origin; small request
bodies held until the request ends, large ones streamed; HTTP/2 to the
edge. It says what was not run and why. No host, zone setting, access
configuration or reachability fact is in it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 2, 2026 •

Copy link
Copy Markdown

Codex Review Summary

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

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-02T07:46:55.786169Z ef4ecc7 PR opened
🔒 Security Review ✅ Completed 2026-11-02T07:47:27.883451Z ef4ecc7 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.

@connorwang
connorwang merged commit 7d0ab55 into main Nov 2, 2026
1 check passed
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