Skip to content

Validate configuration against transport capabilities at startup #7

Closed
4 of 4 issues completed

Description

@thomhurst

Complete D24 startup capability validation (superseding D14), design §2.3.

The endpoint/ordering foundation shipped in #77; failure and batch selection shipped in #88 and #99. All four native sub-issues (#73–#76) are closed. Send, durable enqueue, commit-time dispatch and recovery prerequisites have now shipped, including #135 for #31 and #161 for #33. There is no remaining prerequisite blocker.

Remaining acceptance criteria

  • Declare a route's required scheduling delay and validate native MaxDeliveryDelay boundaries or a registered durable outbox scheduler at startup.
  • Declare the transaction mechanism explicitly: native broker transaction availability and database outbox durability are distinct guarantees. Validate a native requirement against Transactions; validate an outbox requirement against a registered transaction executor and enforce an active outbox unit during execution. Native transaction ownership stays with the native client.
  • Validate actual per-send DeliverAt, including middleware changes, before serialization or side effects. Persisted schedules require an actual due-row worker, even when the broker supports native scheduling. Commit-only dispatch is insufficient.
  • Test native selection, exact delay boundaries, fallback selection, missing executors, matching store/ordered-lane configuration, and actionable startup errors naming route, destination and transport. Include actual durable scheduled dispatch.
  • Reuse the existing capability cache; preserve AOT and no added per-message capability discovery. Do not introduce validation-only user switches without an execution path.

Native transactions must not silently fall back to a database outbox. The route declaration checks availability; it does not begin or commit a native transaction. The application uses the native client's transaction configuration. This explicit distinction resolves the earlier ambiguous “native Transactions or outbox” wording without weakening either guarantee.

Activity

  1. added
    phase-0: coreCore abstractions, pipeline, generator, testing
    P1High priority
    on Oct 31, 2026
  2. thomhurst commented on Nov 1, 2026

    @thomhurst
    OwnerAuthor

    Rechecked every former child against fresh origin/main. #73 shipped in #77. The executors needed by #74–#76 have not shipped, so there is no satisfied external condition to unpark.

    Consolidated the full #74 criteria into #9 and #76 criteria into #11, then closed those validation-only waiting issues as superseded. Moved #75's complete scheduling/transaction criteria here and closed #75, removing the parent-with-one-child chain. Removed the stale #73 dependencies, and the shipped #62 dependency from #9. Verified this issue has no open children and has native prerequisites #5, #28, #9 and #11.

    #5 is delivered by open PR #70, whose lock is held by another worker. Work independent of that send prerequisite is extracted into #80 and implemented in draft PR #83: typed exception rules, predicates and fallback classification, with tests, Native AOT smoke coverage and a zero-allocation benchmark. #9 retains retry execution, D24 integration, metadata and failed-attempt send buffering. This issue remains open for the scheduling/transaction work and the linked D24 integrations; no capability behavior is claimed as shipped by consolidation.

  3. 5 remaining items

  4. thomhurst commented on Nov 1, 2026

    @thomhurst
    OwnerAuthor

    Rechecked all four closed native children and the remaining parent criteria against origin/main 668d1229edc6842fcce539a1b89cf23a895c060b (short name 668d122). This issue is not complete and must remain open:

    I claimed and inspected #7, then attempted to work its linked dispatch prerequisite; PR #135's lock prevents that work in this unit. No validation-only flags or unsupported fallback claims were added. The scheduling/transaction declaration, exact-boundary selection, missing-executor diagnostics and corresponding tests remain owned here after executable dispatch is available. No source changes or test runs in this audit. Removed this unit's claim before releasing its lock.

  5. added and removed on Nov 1, 2026
  6. thomhurst commented on Nov 2, 2026

    @thomhurst
    OwnerAuthor

    The previous blocker is cleared: #135 merged for #31, and #161 merged for #33. All four native children remain closed. I audited their parent's remaining criteria against origin/main e7c198d: route scheduling and transaction declarations were still missing, so closing the parent would have been premature.

    Claimed and implemented the remaining work in draft PR #184 (head dbe5098), which closes this issue when merged. Removed the closed dependency links and refreshed this issue's body to the remaining criteria. Native transaction availability and database outbox durability are explicit separate requirements; scheduling fallback requires actual registered due-row workers. Runtime guards cover actual schedules and active transactions, with matching store/lane validation and actual PostgreSQL due-row execution tests.

    Release build passes with zero warnings/errors. Full suite passes 964 tests, zero failed/skipped; after two extra startup cases, final complete core suite passes 553 tests. Native AOT win-x64 publish/execution and npm ci/documentation build pass. Detailed validation, scope limits and hash-verified evidence location are in the PR. Claude is CLEAR for this head; Codex review requested. This is implemented work waiting for draft review, not another deferral. The issue claim remains while the PR is open; this unit releases its locks.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    P1High priorityarea: coreCore libraryin-progressClaimed by an agentphase-0: coreCore abstractions, pipeline, generator, testing

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions