Skip to content

build scripts still read the gone provable-contracts sibling path: serve codegen (arch-requirements, tensor-names), graph, verify, verify-ml (#4369 class) #4380

Closed as not planned

Description

@noahgift

#4369 fixed this defect class for the binding.yaml producers. The #4369 quorum found more build scripts that still read a provable-contracts sibling path, which has not existed since APR-MONO. When the file is missing they fall back silently.

site reads fallback when missing
crates/aprender-serve/build.rs:507 (generate_arch_requirements_file) ../../../provable-contracts/contracts/architecture-requirements-v1.yaml hand-written arch_requirements.rs (build warns [PMAT-228] … not found; using hand-written … fallback)
crates/aprender-serve/build.rs:818 (generate_tensor_names_file) ../../../provable-contracts/contracts/tensor-names-v1.yaml stub
crates/aprender-graph/build.rs:3 ../../provable-contracts/contracts no assertions emitted
crates/aprender-verify/build.rs:3 same same
crates/aprender-verify-ml/build.rs:3 same same

Both serve YAMLs exist in-tree at contracts/. Repointing the serve reads changes the generated code (YAML-generated instead of hand-written), so each change needs a diff of the generated output and a serve test run. That is why these were not folded into #4369.

Done when every build script reads in-tree contracts/ and fails loudly when the file is missing inside the monorepo (the same guard shape as #4369), and no build prints the PMAT-228 fallback warning.

Activity

  1. added this to the 0.70.0 milestone on Sep 25, 2026
  2. noahgift commented on Sep 25, 2026

    @noahgift
    ContributorAuthor

    Fixed on e6/4380-build-contracts-paths @04b158441, stacked on #4369's GH-4369-producers-repoint @4bd3a8448 (both touch serve build.rs).

  3. modified the milestones: 0.70.0, 0.70.1 on Sep 26, 2026
  4. modified the milestones: 0.70.1, 0.71.0 on Oct 4, 2026
  5. added
    P1High priority
    and removed
    P0Critical priority
    on Oct 14, 2026
  6. noahgift commented on Oct 14, 2026

    @noahgift
    ContributorAuthor

    P0 to P1 (2026-10-14 P0 triage): P0 now means it blocks the next release or carries the operator's own words on it; this issue does neither, so it stays on the 0.71.0 milestone at P1.

  7. noahgift commented on Oct 14, 2026

    @noahgift
    ContributorAuthor

    Folded into #5306 as a checklist row (TRIAGE-100, 2026-10-14): the open-ticket cap is 100, so this ticket is now tracked on that master and closed as not planned. Nothing is lost: reopen it when its work resumes, and an open PR for it reopens it. Pushed branch: e6/4380-build-contracts-paths.

    Agent: aprender-clerk

  8. noahgift commented on Oct 14, 2026

    @noahgift
    ContributorAuthor

    Row moved: #5306 was split into named masters (TRIAGE-100 master naming), so this ticket's checklist row is now on #5326.

    Agent: aprender-clerk

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

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions