Skip to content

DO NOT MERGE: Axum integration RC - #462

Draft
ChristianPavilonis wants to merge 755 commits into
mainfrom
rc/aws-prospect-review-20261110
Draft

ChristianPavilonis wants to merge 755 commits into
mainfrom
rc/aws-prospect-review-20261110

Conversation

@ChristianPavilonis

@ChristianPavilonis ChristianPavilonis commented Nov 10, 2026 •

Copy link
Copy Markdown
Collaborator

DO NOT MERGE. Draft integration checkpoint, not a release or deployment qualification.

Purpose and review order

Combine the existing demo framework work under one reproducible public SDK revision for the separate Trusted Server extraction.

Selected stack465 is ready for review: #275 → #406 → #407 → #409 → #414 → #422 → #439 → #454. This integration does not replace those reviews or merge any constituent into main. #454 remains a standalone prototype, not production KV Geo. CloudFront remains the demo serving provider.

Closes #461. Historical RC #431 and recovery refs remain preserved. Existing packaging/timing review units #401/#389 remain separate. No new buffer-group, codec-subset or phase-timeout experiment is included.

Exact checkpoint

Branch: rc/aws-prospect-review-20261110.

Integration commit: 456313675b6a85e11acea870240f6a6d869f1137.

Tree: 3462994b652ac406fff8a93e2b0b36525e03876f.

Unit Included immutable review head
#275 foundation a7d7fd0f2face027e3810ed67e80f6341fcf68b6
#406 hosting 9f090e573206cf0d8c21c1ce0067afffd69f12db
#407 buffered JSON 8a2a0b7d7d268c6e2b7269dc49e02c47c5f04b8a
#409 diagnostics/trusted ingress 5bbff2bf6d6d853b470f76e7293b7ecfa55476f5
#414 native AWS stores c66f93f118141a2ed7469a8ab96b12902f3854e6
#422 native celld stores f9b0f20c6857d2e638bcfe7bf1edaa5af5425bfb
#439 Geo/CloudFront 414e52ae41ee95880fd11238a22ad2dc944f44c2
#454 standalone KV prototype c52bdaf34bb8694a6f2ee5b584ef127379db4cb0
#460 minimum TS outbound compatibility cec19886598c61e944e861c0515bb0f3ff4bb800
#463 conditional/physical celld records b18a44d0a63790e8a16fe14737afa0a2053a5f5b
#464 admitted-error finalization 96c21d731501370044f11ca5832e85701e79a421
Existing packaging/timing ports 2510ecc91dbef4a6b6d6b8c725b63110773d69ba, 7c07b8e777d9e0872c3bd9388df7ea7b2f189497

The three follow-on review heads are explicit ancestors, not hidden conflict-resolution changes. #460 reuses the completed clock/readiness/tagged-platform-default unit directly required by TS callers; it does not include later optional SDK experiments. #453/MaxMind is excluded.

Retained fixes

  • Preserve current body ownership, immutable ingress/provenance, grants, cancellation and deadline contracts.
  • Retain native-only scaffold gating and existing target compilation fixes.
  • Carry the reviewed AWS typed timeout classification and compatible optional native dependency cohort, without changing retry behavior or suppressing warnings.
  • Retain the test-only full-upload response reader and HTTP-readiness polling corrections.
  • Keep the pre-dispatch documentation alignment that removed stale retired API names. The strict legacy guard is not relaxed.

Checks and limits

At this exact integration checkpoint, an isolated local build records:

  • Formatting and workspace all-target/all-feature strict Clippy pass.
  • AWS provider suite: 78 passed, zero failed/ignored.
  • Axum: 488 unit, 28 contract, six AWS startup and four celld startup tests passed.
  • Production hosting: 35 passed, one failed. native_source_bound_single_proxy_and_mapped_cidr_match_only_owned_peers received no expected handler client field, asserted Null versus 127.0.0.1. This failure is unclassified and not waived. It prevents a clean hosting/readiness claim for this integration.

The Core tree is unchanged from the earlier 7f9abaca checkpoint, which passed all six required commands, the legacy/docs guards and prototype checks. Those receipts remain bounded to their tested tree or unchanged relevant inputs; they are not a whole-workspace pass for this new checkpoint. An initial shared-target build had a source/artifact API mismatch; its failed logs were retained, and the isolated rebuild compiled the expected API without a source change.

Fresh hosted results remain visible. No current complete workspace pass, TS compatibility, browser/consent, live ALB/CloudFront security, production identity persistence, fleet durability or deployment acceptance is claimed. The separate TS port must establish its own matching-pin checks.

No deployment, live input switch, registry publication, infrastructure mutation, old-RC retirement or recovery-ref deletion is authorized by this PR.

TS cutover follow-up, November 11

Integrates the refreshed existing stack and required conditional-record/finalization review heads. Preserves historical RC #431 and its semantic tag. This RC is the target for the next semantic Axum prerelease after hosted qualification.

Current head: 36f8e9c9c2c93661aaa73f2ca956cec3bc9e4c92.

Local combined-RC qualification at 36f8e9c9c2c93661aaa73f2ca956cec3bc9e4c92: workspace tests 2,947 passed / 6 ignored; all-feature Axum 568 passed, including 36 production-hosting, 6 AWS startup and 4 celld startup cases; core doctests 19 passed / 13 ignored; strict workspace Clippy, formatting, feature compilation and Spin WASM check passed under Rust 1.98.1. Narrow TS consumer proof under Node 24.20.0: all four real proxy tests and typed prepared config/secrets/router startup passed. This is not final TS-stack/image/deployment qualification. Fresh hosted checks are still required.

Current foundation and fixture checkpoint

Current RC source is 5d7c7fbe09503e3d76c42e2589f7705ac839be72. It retains concurrent #275 review closeout b97efec1, the received-head/startup-router APIs, complete byte-bounded wire evidence and atomic framing receipts. The latest fixture-only repair is owned by #414 at e9181716; it fixes the reproduced AWS timeout test listener-lifetime race without changing production classification, timeouts or SDK retries.

Predecessor 9e9da0c6 passes all 13 local gates, including the full Fastly CI suite, with 2,947 workspace passes and 661 harness passes. Current RC workspace tests, strict AWS lint and formatting pass again. Its exact-head full Fastly recheck and fresh hosted checks are running. Local Fastly uses the explicitly repaired Viceroy, not a stock-runtime or hosted claim.

The refreshed TS #1506 consumer includes ff04dfb1 and passes 4 proxy, 1 prepared config/secrets/router and 39 Axum route tests against 9e9da0c6. This is a private path-overlay probe, not final tag-bound TS qualification. No new semantic tag, GitHub release, main merge or deployment has been performed.

Latest RC qualification source

Current source is 4407d94130a9b752a70528b6c6f9c8fe3c10b81d, tree ecf59797036cd36b6d9af411239dc6fe4ce0b479. It includes #275 callback-fixture repair 14a6ca8b in addition to the preceding AWS fixture repair. Predecessor 5d7c7fbe reached 34 successful hosted checks; its remaining Fastly fixture failure was reproduced locally and corrected without changing production behavior or weakening stale-scope assertions. At the new RC, all 325 Fastly WASM unit tests, strict WASM Clippy and formatting pass. Full local Fastly CI and fresh hosted qualification are running. No new semantic tag or deployment is claimed.

aram356 and others added 30 commits October 29, 2026 22:20
Exercise independent decoded, encoded and buffered limits through the real Spin wire path while retaining the redirect inventory and local-only qualification scope.

Recognize interrupted Fastly test records without weakening sentinel checks, and drain bounded recovery request bodies in the controlled startup responder.
# Conflicts:
#	crates/edgezero-test-harness/src/main.rs

This branch has not been deployed

No deployments
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.

Track review-stack AWS demo integration checkpoint

3 participants